VoiceOver bug with replacing app's main menu
VoiceOver bug with replacing app's main menu
- Subject: VoiceOver bug with replacing app's main menu
- From: Bryan Smart <email@hidden>
- Date: Tue, 23 Feb 2010 01:02:01 -0500
- Acceptlanguage: en-US
- Thread-topic: VoiceOver bug with replacing app's main menu
I'm not sure if this is the right place to report a bug. If not, please tell me where to send it.
I'm working on a Cocoa application that must occasionally switch between two entirely different menu bars. When the time comes to make the switch, I pass the new menu to NSApp setMainMenu. The menu switches just fine, but VoiceOver won't recognize that portion of the menu bar any longer. To VoiceOver, the application area of the menu bar seems blank. When I press VO-M, I don't even hear an announcement that the menu has been activated. If I press VO-m again, though, I'll cycle through the other regions (Spotlight, the task area, etc), but, once I cycle back to the application menu bar area, VoiceOver doesn't read anything.
If I turn VoiceOver off, and then immediately turn it back on, then it will go in to the new menu bar just fine with VO-m. However, once I must switch the menu bar again, VoiceOver won't see the menu bar all until I reload it.
I know that setting an entirely new menu bar isn't a common activity at run-time, but I understood that it was an acceptable action if necessary. Is this a VoiceOver bug? Is there any way that I can work around it by sending it some sort of notification to reparse the menu bar? I don't want to tell users that they'll need to turn VoiceOver off and back on, since the switch happens quite frequently in this app.
Bryan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden