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
I've now finished editing attribute data and want to go back to the map (saving my work). The obvious button that's visible is 'Back' but if I press that, my point is lost (I have done this many times by accident). To save I have the (1) minimise the KB then (2) hit save.
Perhaps we can put the save button at the top of the page so we have either 'Save' or 'Cancel' there?
The text was updated successfully, but these errors were encountered:
@mostlyAtNight How about that upon clicking "Back" we would check if there are any changes to attributes, and if there are, we would ask the user whether to save the changes [yes] / [no] / [cancel]
That would avoid the need to have the bottom toolbar always visible (taking up vertical space) and also avoid having to move the controls around...?
Currently the idea to solve this is to have Cancel/Save buttons in the header, so they are always visible:
This should also avoid the common source of problems when users edit something, then click back button, forgetting to save the changes. With this approach they would explicitly choose whether to save or discard changes...
Check this:
I've now finished editing attribute data and want to go back to the map (saving my work). The obvious button that's visible is 'Back' but if I press that, my point is lost (I have done this many times by accident). To save I have the (1) minimise the KB then (2) hit save.
Perhaps we can put the save button at the top of the page so we have either 'Save' or 'Cancel' there?
The text was updated successfully, but these errors were encountered: