Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Graphical timetable (Streckengrafik) renders only one trainrun segement #320

Closed
3 tasks done
aiAdrian opened this issue Oct 23, 2024 · 0 comments · Fixed by #325
Closed
3 tasks done

[Bug]: Graphical timetable (Streckengrafik) renders only one trainrun segement #320

aiAdrian opened this issue Oct 23, 2024 · 0 comments · Fixed by #325
Assignees
Labels
bug Something isn't working

Comments

@aiAdrian
Copy link
Collaborator

aiAdrian commented Oct 23, 2024

Preflight Checklist

Bug type

Functionality

Which version are you using

2.8.0

Operating system

Windows

Browser / Browser version

Chrome

What happened?

In the graphical timetable (Streckengrafik), trainrun consisting of multiple segments are not displayed completely. Only the first segment is rendered, while all subsequent segments are missing in the final graphical timetable graphic. This issue particularly affects trainruns that, for example, travel from A via V1 and V2 to B, and have a partial cancellation between V1 and V2. Such partial cancellations cause the missing segements in the final rendering. Thus they are not displayed correctly, resulting in an incomplete representation of the entire trainrun (path).

Steps to reproduce the issue

  1. Open atteched JSON two_part_trainrun.json
  2. Select ECFull_Path
  3. Open graphical timetable (Streckengraphic)

The trainrun GTwo_Part_trainrun is not correctly rendered due to the multi-segment issue. The trainrun has one segment starting [RTR - OL - ZUE] and a second segment [BAA, ZF, ZG, SS]. The second segment is missing, as shown in the image below:
image

Related issue

This issue is related to issue #319, which is currently closed. After correcting the reported bug, please check whether issue #319 needs to be reopened.

@aiAdrian aiAdrian added the bug Something isn't working label Oct 23, 2024
@aiAdrian aiAdrian self-assigned this Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant