Ticket #988 (closed defect: wontfix)
Opened 2012-02-21T15:37:18-06:00
Last modified 2014-08-24T17:15:01-05:00
More intelligent syncing between ShadowMenu and UI-specific menus
Reported by: | curtis | Owned by: | curtis |
---|---|---|---|
Priority: | minor | Milestone: | imagej2-unscheduled |
Component: | UI Framework | Version: | |
Severity: | minor | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | #985, #1630 |
Description
Currently, when a ShadowMenu change and fires a subclass of MenuEvent, the UIService intercepts the event and does a total rebuild of the UI's menu by calling UserInterface.createMenus() again. While this works, it is certainly overkill and may have performance implications when menu changes happen rapidly.
Better would be expand the MenuCreator class hierarchy to support surgical updates to UI-specific menu structures. The "MenuCreator" would become more of a "MenuSyncer" and would bidirectionally unite the UI-specific menu with its linked ShadowMenu.
Change History
comment:1 Changed 2012-02-21T15:41:06-06:00 by curtis
comment:2 Changed 2012-02-23T19:44:16-06:00 by dscho
Maybe I should have commented here instead on bug 985? (I'm referring to http://code.imagej.net/trac/imagej/ticket/985#comment:1)
comment:3 Changed 2012-02-24T15:34:55-06:00 by curtis
- Blocking 985 added
comment:4 Changed 2012-03-05T15:00:29-06:00 by curtis
- Milestone changed from imagej-2.0-beta3 to imagej-2.0-beta2
Moving to beta2, to match ticket #985.
comment:6 Changed 2012-07-12T11:08:15-05:00 by curtis
- Blocking 1291 added; 1162 removed
- Milestone changed from imagej-2.0.0-beta3 to imagej-2.0.0-beta4
comment:10 Changed 2012-08-03T10:22:25-05:00 by curtis
- Blocking 1291 removed
comment:11 Changed 2012-08-03T10:23:56-05:00 by curtis
- Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta5
comment:12 Changed 2013-01-22T15:41:01-06:00 by bdezonia
- Blocking 1630 added; 1356 removed
- Milestone changed from imagej2-b7-ndim-data to imagej2-unscheduled
comment:13 Changed 2014-08-24T17:15:01-05:00 by curtis
- Status changed from new to closed
- Resolution set to wontfix
Punting on this for now. We can tackle it later, only as needed.
Also, this change will solve an issue discussed on the mailing list: