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

Improve LTN Turn Restriction editing UX design #1110

Open
andrewphilipsmith opened this issue Sep 6, 2023 · 0 comments
Open

Improve LTN Turn Restriction editing UX design #1110

andrewphilipsmith opened this issue Sep 6, 2023 · 0 comments
Labels
design-needed Visual / UX design help needed ltn

Comments

@andrewphilipsmith
Copy link
Collaborator

Based on feedback here: #1091 (review)

The UX of only being able to select a destination road on
one end is confusing to me. When you hover on a road in the neutral
state, roads on both endpoints are highlighted, but when you click, the
closer one wins.

## Option 1

My first preference might be to get rid of the endpoint distinction
and just let the destination road exist on either end. I remember
discussing this and don't remember the rationale... was it due to
ambiguity with complex TRs and sequences of multiple roads where some
road might be shared?

This would require finding a solution for #1108

Option 2

As a second option, what if we change the hover behavior to make it
clear which side of the road the cursor is closer to, so the click
becomes expected?

This would require calculating the hitboxes for each half-road segment. This would be a faff, but it is possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-needed Visual / UX design help needed ltn
Projects
None yet
Development

No branches or pull requests

2 participants