#6571 closed enhancement (invalid)
Feature idea: use another undo-cue for single transactions (move, selection,...)
Reported by: | dieterdreist | Owned by: | dieterdreist |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | undo cue selection move | Cc: |
Description
Currently selection commands (like add to selection, new selection, ...) are not stored in the undo-cue, which is fine for many working flows. If you make bigger selections it would be sometimes nice to be able to undo a selection. A possible solution could be to reuse the undo machanism a second time just for selection.
This could be also extended to other operations which currently are merged to one single undo-operation: e.g. for distinct move-undo (currently all move commands except the last are ignored in undo). There would be 2 undos: one where only distinct operations (like add node, move a node, etc.) are undone (like undo works now) and one undo where every single operation like add a node to a selection, move a node several times (each intermediate step (mouse release) would be stored) can be undone.
Attachments (0)
Change History (5)
comment:1 by , 14 years ago
Summary: | Feature idea: use another undo-cue for selection-commands → Feature idea: use another undo-cue for single transactions (move, selection,...) |
---|
comment:3 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
comment:4 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | needinfo → closed |
Sorry for the noise. I hadn't yet discovered this selection history from the selection tab (indeed the button is greyed out, but is working nonetheless).
The remaining issue might be the behaviour of JOSM when moving objects (only 1 movement is registered in UNDO). I am not sure if this is really helpful (actually I guess there is dedicated code to achieve this, because usually all movement actions would automatically go to the undo-cache). But I don't consider this a very important topic, so I closed this thread for now.
Cool that there is already a selection undo!
comment:5 by , 14 years ago
I did not notice selection history too before I write half of UndoSelection code :)
Current state:
There are "Undo selection" and "Select last modified nodes"/"Select last modified ways" features in Utilsplugin2 plugin (Ctrl/Shift/Alt - Z combinations, selection menu). There is also Selection History in JOSM Core (black triangle button in selection panel).
Changes of selection are not stored in undo command list (they do not change the map), and commands are stored in non-splittable groups (when 150 nodes are moved, why should we undo it one by one?).
What additional actions you propose?