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.

Bug 10816 - Update state of the menus before they are shown to the user
Summary: Update state of the menus before they are shown to the user
Status: RESOLVED DUPLICATE of bug 17597
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@platform
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2001-03-29 06:43 UTC by Jaroslav Tulach
Modified: 2008-12-22 21:52 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2001-03-29 06:43:53 UTC
There is a need to update the state of popup menus and also menus shown from
main window before they are shown to the user. 

1. focus follows mouse mode (with a delay to update the actions) needs this to
synchronize the current focus with state of actions

2. the menus should be as accurate as possible. This will reduce the changes to
the menu when it is already visible

There is a need to communicate between openide and core, so I would suggest some
bridge method to cross the gab -
org.openide.actions.ActionManager.synchronizeActions (...), or something like
this.

A problem is to write the code in such a way that for example Explorer will
still remain separable from the rest of the openide.jar.
Comment 1 Jaroslav Tulach 2001-03-29 06:46:06 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.
Comment 2 Jan Chalupa 2001-05-06 08:10:19 UTC
Target milestone -> 3.3
Comment 3 _ ttran 2001-10-19 07:30:46 UTC
something very desirable, but not a P2 IMHO.  Added PERFORMANCE keyword
Comment 4 Peter Zavadsky 2001-11-13 16:44:10 UTC
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 ***