Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 226005 - [update policy] The "Update Policy ->" menu in variables, registers views is inconsistent.
Summary: [update policy] The "Update Policy ->" menu in variables, registers views is ...
Status: CLOSED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf (show other bugs)
Version: 0 DD 1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: DD 1.0   Edit
Assignee: Ted Williams CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 219124 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-04-07 13:28 EDT by Pawel Piech CLA
Modified: 2014-01-29 21:17 EST (History)
2 users (show)

See Also:


Attachments
Patch with fix. (34.32 KB, patch)
2008-05-01 18:26 EDT, Pawel Piech CLA
cdtdoug: iplog-
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Pawel Piech CLA 2008-04-07 13:28:50 EDT
The "Update Policy" sub-menu available in the registers and variables views allows the user to select when the view should be updated.  This menu is populated based on the current input into the view and it shows the list of updated modes supported by the current view model. 

The problems are:
- Sometimes the action for this menu does not show the sub-menu at all.
- When a new mode is first selected in the menu, the selection doesn't stick.  The new mode has to be selected again the second time for the mode to actually take effect.
- The action menu is not registered for the Expressions view at all, although the view should be able to support different update modes.

If all problems cannot be addressed at once, additional bugs may be filed.
Comment 1 Pawel Piech CLA 2008-05-01 18:18:23 EDT
*** Bug 219124 has been marked as a duplicate of this bug. ***
Comment 2 Pawel Piech CLA 2008-05-01 18:26:37 EDT
Created attachment 98386 [details]
Patch with fix.

I fixed the various issues with this menu, but in order to do that I had to turn the menu back to a static menu with individual actions for each update mode.  Most of the problems with the menu came from the fact that the action (and the sub-menu) was not initialized before the menu was shown.  
To make this a dynamic menu we would need to convert it to use the command framework, and we would need the debug framework to provide us with a debug context (see bug 229219).
Comment 3 Pawel Piech CLA 2008-05-01 18:29:01 EDT
I committed the fix.  Ted could you plesase review.
P.S. I also did some cleanup in the plugin.xml.
Comment 4 Pawel Piech CLA 2008-08-13 13:06:53 EDT
Closing out 1.0 bugs.