• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: GUIscritpting, Pages and PDF
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GUIscritpting, Pages and PDF


  • Subject: Re: GUIscritpting, Pages and PDF
  • From: KOENIG Yvan <email@hidden>
  • Date: Thu, 24 Jan 2008 21:50:33 +0100


Le 24 janv. 2008 à 20:52, Bill Cheeseman a écrit :

on 2008-01-24 1:16 PM, KOENIG Yvan at email@hidden wrote:

[MISMATCH] bouton de menu "PDF" (menu button -2147483648)

The "[MISMATCH]" tag is inserted by UI Browser when the target application
contains an Accessibility API bug, commonly known as a "parent-child
mismatch." What this usually means is that the target application reports
one version of the UI element hierarchy when it looks "down" from the root
application UI element, as UI Browser's browser view does, and a different
version of the hierarchy when it looks "up" from a leaf element under the
mouse on the screen. To be correct, the hierarchy must be identical in both
directions. This kind of bug is very, very common in a large number of
applications.


You will get another clue as to the location of the mismatch if you use UI
Browser's screen reader mode, or Apple's Accessibility Inspector, to look
"up" the hierarchy. Basically, somewhere in the menu hierarchy there is
probably a child who thinks a particular UI element is its parent, but that
parent UI element thinks some other UI element is its child.


You'll find a little more information about this in UI Browser's Help.

Depending on the nature of the bug in the target application, it may still
be possible to use GUI Scripting to access the UI element you're looking
for. But in your case, that apparently is not possible.


The only things you can do about this are:

1. File a bug report with Apple about the target application. If you do
that, be sure to include a complaint that the target application is not
scriptable in its own right, which is why you had to resort to GUI Scripting
in the first place.


2. Look for an alternative way to script what you're doing. Sometimes, for
example, you can send a keyboard shortcut instead of clicking a menu item.


--


Thank you, glad to get a response from Mr UI Browser himself ;-)

a -- I will file a bug report. But I am acustomed to LLLLLLLOng delays before the correction of this kind of oddity and my correspondant has hundreds of files to print as PDF.

b -- as the menu item has no keyboard shortcut, I will try to define one from the Keyboard and Mouse prefPane .

If it works, I would ask to my correspondant to do the same.

Yvan KOENIG

_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users

This email sent to email@hidden
References: 
 >Re: GUIscritpting, Pages and PDF (From: Bill Cheeseman <email@hidden>)

  • Prev by Date: Re: Copy to clipboard question
  • Next by Date: Re: Copy to clipboard question
  • Previous by thread: Re: GUIscritpting, Pages and PDF
  • Next by thread: Re: GUIscritpting, Pages and PDF
  • Index(es):
    • Date
    • Thread