Menu item issues when programmatically updating an application's main menu
Menu item issues when programmatically updating an application's main menu
- Subject: Menu item issues when programmatically updating an application's main menu
- From: "Mattias Arrelid" <email@hidden>
- Date: Tue, 23 Sep 2008 22:23:31 +0200
Hi list,
We have some code in an application of ours that replaces the main
menu using NSMenu's setMainMenu:. This has been working just fine
since day one but ever since the introduction of Leopard we have
noticed some strange behavior with the "Help" menu. I have also
noticed this behavior in RealPlayer.app and in Flickr Uploadr.app (so
if you want to see it in action, just repeat the below steps in any of
those applications).
The behavior I am about to mention does _not_ occur when the
application is running under 10.4, _or_ if the "Help" menu item is
renamed to something else (like "Helpz"). Now let me try to explain my
problem...
After having set the main menu on startup (using setMainMenu:), the
main menu (and all items in the submenus) works exactly as in every
application. But... after the next (and on each successive) call to
setMainMenu: the "Help" menu item starts to act weird.
When trying to highlight "Help" and then either pressing the left
arrow on the keyboard or moving the mouse left (so that it's now
placed above the "Window" menu) the system first dismisses the "Help"
menu and then very briefly displays the "Window" menu but then
dismisses (closes) it. Re-opening the "Help" menu again and repeating
the above mentioned steps will "repair stuff" - the "Help" menu is
dismissed, and the "Window" menu is shown. The main menu will now work
correctly until next call to setMainMenu: - and then you will have to
repeat the above steps before the "Help" menu works as expected again.
The problem can also be spotted if you try to open the "Help" menu
(after setMainMenu: has been called) and try to perform any of the
items within it - they simple won't work (until you've dismissed the
"Help" menu and the invoking it once again).
Does anyone have a clue what I could do debug this? I'm really puzzled
after having tried to figure out the cause this afternoon...
/ M
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden