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

crash when trying to define stop #5963

Closed
namdre opened this issue Aug 21, 2019 · 1 comment
Closed

crash when trying to define stop #5963

namdre opened this issue Aug 21, 2019 · 1 comment
Assignees
Labels
a:netedit bug netedit:demandElements Label for netedit tickets centered in demand elements p:critical more important that 'important' but not 'blocker' regression Works in previous versions
Milestone

Comments

@namdre
Copy link
Contributor

namdre commented Aug 21, 2019

see bugreports folder.
To reproduce netedit -s net2.net.xml -a stops.add.xml -r train.rou.xml

  • F4, A, click on leftmost edge
@namdre namdre added p:critical more important that 'important' but not 'blocker' a:netedit bug netedit:demandElements Label for netedit tickets centered in demand elements labels Aug 21, 2019
@palvarezlopez palvarezlopez self-assigned this Aug 21, 2019
@palvarezlopez palvarezlopez added this to the 1.4.0 milestone Aug 21, 2019
@namdre namdre changed the title crash when trying to define stop as child element of a flow crash when trying to define stop Aug 21, 2019
@namdre namdre added the regression Works in previous versions label Aug 21, 2019
@namdre
Copy link
Contributor Author

namdre commented Aug 21, 2019

  • on linux there is a warning instead of a crash but the stop still cannot be defined
  • was working in 1.2.0 (except for from-to-flows which could not be loaded in 1.2.0)

@namdre namdre modified the milestones: 1.4.0, 1.3.1 Aug 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:netedit bug netedit:demandElements Label for netedit tickets centered in demand elements p:critical more important that 'important' but not 'blocker' regression Works in previous versions
Projects
None yet
Development

No branches or pull requests

2 participants