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
all
Browser / Browser version
all
What happened?
When at a node the trainrun should not stop the user can toggle the Non-stop / stop in the transition element. There are several cases to ensure correct handling the behavior
Case 1: Non time are locked arround the node (trainrun section before and after)
Works fine
Case 2: The after section departure/arrival time is locked
DOn't work fine. If this is the case the application has to check whether the before section arrival/departure time is lock or not. If not locked the time change has to be done in the backward direction
Case 3: The before section departure/arrival time is locked
Don't work fine:
Case 4: Both side departure/arrival time are locked
Works fine. The time can not be changed, thus the business rule that the arrival - departure time difference has to be zero is not satisfied, thus:
correct.
Steps to reproduce the issue
Reproduce the above described 4 cases and test all of them.
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Bug type
Functionality
Which version are you using
2.5.0
Operating system
all
Browser / Browser version
all
What happened?
When at a node the trainrun should not stop the user can toggle the Non-stop / stop in the transition element. There are several cases to ensure correct handling the behavior
Case 1: Non time are locked arround the node (trainrun section before and after)
Works fine
Case 2: The after section departure/arrival time is locked
DOn't work fine. If this is the case the application has to check whether the before section arrival/departure time is lock or not. If not locked the time change has to be done in the backward direction
Case 3: The before section departure/arrival time is locked
Don't work fine:
Case 4: Both side departure/arrival time are locked
Works fine. The time can not be changed, thus the business rule that the arrival - departure time difference has to be zero is not satisfied, thus:
correct.
Steps to reproduce the issue
Reproduce the above described 4 cases and test all of them.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: