Re: Issue with process names
Re: Issue with process names
- Subject: Re: Issue with process names
- From: Shane Stanley <email@hidden>
- Date: Thu, 09 Feb 2012 16:55:19 +1100
On 09/02/2012, at 4:23 PM, Brian Christmas wrote:
>> But that still doesn't answer the question of why a script has to address it as application "Adobe Acrobat Pro", not application "AdobeAcrobat".
So I did a search and found this quote from Bill Cheeseman on the implementors list a couple of years ago:
> Technically, the correct
> technique to emulate what AppleScript does is (1) if the application is
> running use the CopyProcessName or GetProcessInformation function to get the
> process name (see -processNameForPid:), otherwise (2) call the
> FSGetCatalogInfo function with the appropriate FSRef and use the
> LSFindApplicationForInfo function to get the exact file name." I got the
> "technically" information in that comment from Chris Nebel, but I can't find
> his e-mail now -- it must be 4 or 5 years old. I believe he indicated that
> AppleScript used obsolete (even then) methods to generate this information
> but that there were no plans (at that time) to change it.
--
Shane Stanley <email@hidden>
'AppleScriptObjC Explored' <www.macosxautomation.com/applescript/apps/>
_______________________________________________
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