id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
6571	Feature idea: use another undo-cue for single transactions (move, selection,...)	dieterdreist	dieterdreist	"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."	enhancement	closed	normal		Core	latest	invalid	undo cue selection move