-
Notifications
You must be signed in to change notification settings - Fork 85
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
UI: Pedestrian Tool #40
Comments
Toggle existing crossingsThe current UI (in junction restrictions) is somewhat clunky, with a big icon floating above the map. IMO it would be nicer if I could interact with crossings themselves. To achieve this, an outline (like #33, lane outline, but for crossings) would be drawn around the crossing or just at the end of the segment on which the crossing exists. The user clicks in the outline to toggle the crossing. The toggle crossing feature should also work with crossings at road-type changes and any crossings manually added at nodes by the user. |
Add new crossingsWith tool active:
Potentially, these 'user created' crossings could be deleted too, maybe with right click in the crossing outline? Source code for existing Crossings mod: https://github.com/bernardd/Crossings |
Ideally the tool would handle things like... Some roads don't have crossing decals; this should be no issue as the UI will be drawing an outline around where the crossing would be (or, ideally, where it is, in the case of roads that do provide crossing decals). Some roads have things like bevelled/tactile pavement (Urbanists' roads) or road studs (UK Roads Revived). |
Eraser toolAs per #38, there will be an eraser tool on the toolbar.
While the Pedestrian Crossings tool is active, user can click the Eraser tool. Then:
|
Boformer thinks he may have a way to hide crossing decal per segment, see #27 for details. |
As per #38, the feature to toggle pedestrian crossings would be moved to it's own tool on the toolbar. This is primarily to reduce UI overload on the Junction Policies tool, but also to create room for some future functionality additions.
The tool serves two main purposes:
At a later date, I suspect this tool would be extended to create #14 (virtual junctions), maybe by right-clicking or Ctrl+clicking a node?
The tool is essentially about pedestrian features, so I think adding the virtual junctions stuff (which is mostly about pedestrian features anyway) at a later date is in keeping with the concept of the tool.
The text was updated successfully, but these errors were encountered: