Re: GUIscritpting, Pages and PDF
Re: GUIscritpting, Pages and PDF
- Subject: Re: GUIscritpting, Pages and PDF
- From: CYB <email@hidden>
- Date: Thu, 24 Jan 2008 23:26:44 -0600
- Thread-topic: GUIscritpting, Pages and PDF
Yvan, whwy not use this
-- AppleScript
tell application "Printer Setup Utility"
set current printer to printer "CUPS-PDF"
end tell
tell application "Pages"
tell document 1
print
end tell
end tell
-- end of AppleScript
The only thing you need is to install the free app printer "CUPS-PDF"
This application is a virtual printer that in an efficient way "print"
anything to PDF is an open source, the linl to download is
http://www.macupdate.com/info.php/id/20219
I hope this help
Salute
Carlos Ysunza B.
Director
Ysunza/Santiago
Visual Communication Automation
Tel. (52)55 5256-0336
email@hidden
http://www.ysunzasantiago.com
http://www.thesecretmexico.com
http://www.softrobot.com.mx
> From: Bill Cheeseman <email@hidden>
> Date: Thu, 24 Jan 2008 14:52:43 -0500
> To: AppleScript-Users Mail <email@hidden>
> Subject: Re: GUIscritpting, Pages and PDF
>
> 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.
>
> --
>
> Bill Cheeseman - email@hidden
> Quechee Software, Quechee, Vermont, USA
> www.quecheesoftware.com
>
> PreFab Software - www.prefabsoftware.com
>
>
>
_______________________________________________
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