You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The is the first step towards a more efficient UI for editing tags in Go Map!!
For the Kaart "MVP"
different buttons depending on selected object type and tags (focused on highways initially)
the first version will be iPad only and the buttons will be added around the edges of the screen
Initial Design Idea
If a way is drawn, a series of buttons will appear on the left(?) side of the screen as "Presets" for a type of way (highways, building, footpath, more button to bring up scrollable popup). After that or if the way is already tagged, other buttons will populate the right(?) edge of the screen as "quick edit" buttons. Some buttons (oneway, reverse, split, join, etc) will simply do the action while other tag buttons will have an alert to edit the tag quickly.
iPhone
I would like to come up with a way this functionality could be brought to iPhone as well.
Initial thought is to have some sort of indication to swipe from the edge to show the menu.
The text was updated successfully, but these errors were encountered:
The is the first step towards a more efficient UI for editing tags in Go Map!!
For the Kaart "MVP"
Initial Design Idea
If a way is drawn, a series of buttons will appear on the left(?) side of the screen as "Presets" for a type of way (highways, building, footpath, more button to bring up scrollable popup). After that or if the way is already tagged, other buttons will populate the right(?) edge of the screen as "quick edit" buttons. Some buttons (oneway, reverse, split, join, etc) will simply do the action while other tag buttons will have an alert to edit the tag quickly.
iPhone
I would like to come up with a way this functionality could be brought to iPhone as well.
Initial thought is to have some sort of indication to swipe from the edge to show the menu.
The text was updated successfully, but these errors were encountered: