Bug 184607 - [Undo] [Contributions] - migrate undo to commands and handlers
Summary: [Undo] [Contributions] - migrate undo to commands and handlers
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-28 13:01 EDT by Susan McCourt CLA
Modified: 2019-09-06 16:11 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2007-04-28 13:01:28 EDT 
Whenever we decide to migrate the operation history action handlers to the commands/handlers story, we should examine whether there should be a default undo handler, and what it should do.  In bug #162964, we discussed that it might be nice to have a default handler which operates on the workbench (global) undo context.
Comment 1 Susan McCourt CLA 2007-06-28 15:56:44 EDT 
Paul, is there any plan afoot to migrate the old workbench actions for 3.4 (or later?)
Comment 2 Paul Webster CLA 2007-06-29 06:52:03 EDT 
Yes, we're going to continue to migrate platform actions to commands/handlers in 3.4 ... for now under bug 171149

PW
Comment 3 Susan McCourt CLA 2007-06-29 12:39:53 EDT 
assigning 3.4 milestone
Comment 4 Susan McCourt CLA 2008-03-18 12:50:04 EDT 
Paul, I'm removing the 3.4 milestone since I'm not really looking for things to do for 3.4.  Can you ping me via this bug if it becomes important to do this?
Comment 5 Susan McCourt CLA 2009-07-09 17:19:26 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:11:50 EDT 
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.