[josm-dev] Do we need some principles for JOSM interface design?
Frederik Ramm
frederik at remote.org
Sun Oct 14 22:14:40 BST 2007
Hi,
> > Storing the full selection for each step of the undo history would be
> > too expensive, memory-wise, but a kludge like "if selection consists
> > of only one node, store it and include it in undo" might be workable.
>
> Perhaps not if changes to selection where handled as Commands.
Might do but it would have to be engineered very well. A simple search
with a few letters entered can easily yield thousands of selected
objects, and users are unlikely to press "undo" afterwards if they
find they don't need that selection. Repeat that a few times and your
stack is full...
Bye
Frederik
--
Frederik Ramm ## eMail frederik at remote.org ## N49°00.09' E008°23.33'
More information about the josm-dev
mailing list