Re: Menu bug?
Re: Menu bug?
- Subject: Re: Menu bug?
- From: Bill Cheeseman <email@hidden>
- Date: Sun, 16 Mar 2003 15:25:03 -0500
on 03-03-15 2:39 PM, Bill Cheeseman at email@hidden wrote:
>
I now have a working workaround that substitutes the menu for the menu item
>
whenever I get the path based on GetElementAtPoint from a submenu or a menu.
>
That's the reverse of what you're describing as the ideal.
My decision to ignore the top-level menu item in the menu bar until this bug
is fixed turns out to be consistent with the current implementation of GUI
Scripting. This command works:
click menu item 1 of menu 3 of menu bar 1 of application "<name>"
This does not:
click menu item 1 of menu 3 of menu item 3 of menu bar 1 of application
"<name>"
Of course, GUI Scripting only works this way because it takes the value
given to it by AXChildren. If you fix AXChildren in time for the final
release of GUI Scripting, all bets are off.
Whatever the merits of the accessibility API's being fixed so as to
faithfully read all duplicate menus and menu items in the menu hierarchy, I
would hope that GUI Scripting would compress them into a single item at each
level of the menu hierarchy, because that's the way real-world scripters
tend to think of them. Something like this:
click menu item 1 of menu item 2 of menu 3 of menu bar 1 of application
"<name>"
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com
The AppleScript Sourcebook -
http://www.AppleScriptSourcebook.com
Vermont Recipes -
http://www.stepwise.com/Articles/VermontRecipes
_______________________________________________
accessibility-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/accessibility-dev
Do not post admin requests to the list. They will be ignored.