You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for an issue that matches the one I want to file, without success.
Bug type
Functionality
Which version are you using
2.5.0
Operating system
Windows 10 Enterprise
Browser / Browser version
Google Chrome / Version 124.0.6367.201 (Offizieller Build) (64-Bit)
Microsoft Edge for Business / Version 124.0.2478.97 (Offizielles Build) (64-Bit)
Mozilla Firefox / Version 125.0.2 (64-Bit)
Input mode
None
Additional settings
No response
What happened?
When a time is changed in the trainrun dialog window, the data update in the network graphic editor (Editor) is executed quickly. However, if the same action is performed in the graphic timetable (Streckengrafik), it takes an eternity (very long). When a time is changed in the pearls view (Perlenkette) and the graphic timetable (Streckengrafik) is active, the update is much faster, even with relatively large network graphics. This suggests that there is some interaction between the trainrun dialog and the graphic timetable component that is causing performance issues.
Steps to reproduce the issue
Open a quite big Netzgrafik
Select a trainrun
Open the graphic timetable (Streckengrafik)
Click on time (number) -> trainrun dialog window opens
Preflight Checklist
Bug type
Functionality
Which version are you using
2.5.0
Operating system
Windows 10 Enterprise
Browser / Browser version
Google Chrome / Version 124.0.6367.201 (Offizieller Build) (64-Bit)
Microsoft Edge for Business / Version 124.0.2478.97 (Offizielles Build) (64-Bit)
Mozilla Firefox / Version 125.0.2 (64-Bit)
Input mode
None
Additional settings
No response
What happened?
When a time is changed in the trainrun dialog window, the data update in the network graphic editor (Editor) is executed quickly. However, if the same action is performed in the graphic timetable (Streckengrafik), it takes an eternity (very long). When a time is changed in the pearls view (Perlenkette) and the graphic timetable (Streckengrafik) is active, the update is much faster, even with relatively large network graphics. This suggests that there is some interaction between the trainrun dialog and the graphic timetable component that is causing performance issues.
Steps to reproduce the issue
Relevant log output
Dependancy
#70
The text was updated successfully, but these errors were encountered: