Bug 138709 - [CellEditors] CellEditorActionHandler doesn't mirror all action state
Summary: [CellEditors] CellEditorActionHandler doesn't mirror all action state
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-04-26 14:30 EDT by Andrew Bachmann CLA
Modified: 2019-09-06 16:15 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Bachmann CLA 2006-04-26 14:30:37 EDT
Currently CellEditorActionHandler uses a property change listener to follow the enablement state of the actions that are used when a cell editor is not enabled.

There are more properties that can be usefully changed, such as IAction.TEXT and IAction.TOOL_TOP_TEXT.  These most affect the usability of undo and redo.

Additionally, the CellEditorActionHandler ActionHandler classes (such as UndoActionHandler) don't update Text, ToolTipText, ImageDescriptor, or DisabledImageDescriptor when the actions are set. (such as setUndoAction)

It seems like it might be possible to address all these issues and simplify the implementation by simply calling setGlobalActionHandler for each action when the controlListener sees an Activate or Deactivate.

Currently we just augmented UndoActionHandler.updateEnabledState to set also the Text, ToolTipText, ImageDescriptor, DisabledImageDescriptor.  We also augmented the ActionPropertyChangeListener.propertyChange to pass along IAction.TEXT and IAction.TOOL_TIP_TEXT updates.  Finally, our local copy of CellEditionActionHandler also includes the fix for Bug 116614.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:15:18 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.