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

Tutorial arrow shows up again if you have to delete a label #3318

Closed
misaugstad opened this issue Jul 27, 2023 · 1 comment · Fixed by #3388
Closed

Tutorial arrow shows up again if you have to delete a label #3318

misaugstad opened this issue Jul 27, 2023 · 1 comment · Fixed by #3388

Comments

@misaugstad
Copy link
Member

Brief description of problem/feature

If you place a label too far from where you're supposed to in the tutorial, you're forced to delete the label. However, once you correct your mistake and finish adding severity/tags to that label and you need to pan, the arrow pointing to that label shows up again and starts flashing! Example flow on the first label below:

First screen when you start
Screenshot from 2023-07-27 11-52-54

Placing a lable too far away
Screenshot from 2023-07-27 11-53-02

Deleting it and placing a label in the correct position, then filling out severity and tags. Everything looks fine
Screenshot from 2023-07-27 11-53-21

Once you start panning, the arrow shows up again
Screenshot from 2023-07-27 11-53-27

This can happen to any of the labels.
Screenshot from 2023-07-27 11-47-27

If the next thing you're supposed to do is pan, it happens when you start panning. If you have another label to add before panning, it will happen if...

You place the first label in the wrong spot
Screenshot from 2023-07-27 12-00-25

Fix it, add tags/severity, place the 2nd label in the correct spot, but DON'T add the tags/severity yet...
Screenshot from 2023-07-27 12-00-48

Then you try and pan...
Screenshot from 2023-07-27 12-01-03

@misaugstad
Copy link
Member Author

@kevinjtwu I'm updating the tutorial to add crosswalk and pedestrian signal labels, and I ended up fixing this bug during the course of that update, so it is now off your plate!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants