Hi Carsten, > What you have found is an optimization for the menu implementation. > Status updates are not very cheap and the current states of the menu > entries are not visible to the user. The menu contains about 300 entries > and can have a significant performance impact for status updates. > Therefore we decided to retrieve the status on demand, means when the > menu gets opened by the user. The menu implementation uses add- and > removeStatusListener for every menu item to retrieve the status and > updates the state. This optimization is not possible for toolbars as > they are visible all the time. I don't think that this optimization can > have a negative impact on a correct implementation. It's just an > implementation detail. The status is retrieved on demand and not updated > whenever a state changed.
thanks for detailed explanation. As a woraround i can add a toolbar icon for every menu command, but this will not help if i have submenu included, and the user opens the submenu before the interceptor is registered ... I will have a closer look when i am back home next weekend... Oliver -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
