This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Update state of the menus before they are shown to the user | ||
---|---|---|---|
Product: | platform | Reporter: | Jaroslav Tulach <jtulach> |
Component: | Window System | Assignee: | issues@platform <issues> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | ttran |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | TASK | Exception Reporter: |
Description
Jaroslav Tulach
2001-03-29 06:43:53 UTC
Tor's comment: I think the trick is to do the menu computation on demand, BUT, before the menu is posted! In other words, once the menu is displayed, it should not change at all (except for due to events unrelated to the menu operation, for example compilation may suddenly complete and that affects the enabled/disabled state of some items in the menu). In other words, when we find out that the user intends to pop up a menu (right mouse click), we compute the menu contents, and when we're done with the whole menu, we post the menu. We should not query actions for their state after the menu has been posted. Target milestone -> 3.3 something very desirable, but not a P2 IMHO. Added PERFORMANCE keyword Changing to task, target milestone, and resolving as duplicate of 17597. There are better described the tasks for Action API changes. *** This issue has been marked as a duplicate of 17597 *** |