Community
Participate
Working Groups
While looking at the different kinds of undo that might be useful in the IDE, there is a category of "mouse accidents" or "wrong key slipups" that could be undone if JFace viewers provided generic undo for navigation operations. Examples include: - changes in selection - expand collapse state in trees - visible item (scrolling) While these kinds of problems aren't as important as data loss, there are times that one wrong move can invalidate a lot of effort that went into getting where you wanted to be. This kind of support could perhaps be available in some place other than Edit>Undo..., probably some kind of affordance on the part itself. Thoughts?
This undo is more valuable than it might seem, especially when you aren't sure what you've just done. Sometimes the user "slips"(during a drag/drop, scroll, key slipup, etc.) and the viewer's context changes radically, and the user is not sure what they have just done. They can see what's available in the Undo menu, and if they in fact changed data (and assuming we support resource-based undo), they can see something like "Undo move Xxx" and realize what they've done. But if there's no data change, and nothing to undo (or something old to undo), then they still aren't sure what they did. If there were a place to undo the gesture at that point, they might see that all they did was scroll, or accidentally expand/collapse something.
cc'ing Boris since this one involves viewers. Boris, I don't this in my 3.3 plans at this time, but wanted you to know about the idea.
"Undo Gesture" would also be useful in workbench windows for e.g. resize, move, detach, attach, maximize, minimize, open, close parts, or even for undoing settings changes like filters, etc. .
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
