Re: controlling remote application question
Re: controlling remote application question
- Subject: Re: controlling remote application question
- From: Steve Roy <email@hidden>
- Date: Tue, 11 May 2004 08:14:35 -0400
On May 10, 2004, at 4:17 PM, Christopher Nebel wrote:
It's not impossible by any means, but it's far from obvious for a
normal user. For a bundled application, the process name winds up
being the name of the actual executable file. For instance, the
relevant bits of Mail look like this:
Mail.app/
Contents/
MacOS/
Mail <-- the executable.
The name of the executable is usually the same as the bundle name
minus the extension, but if it's different, it's in the Info.plist
under CFBundleExecutableName. For what it's worth, this problem
didn't occur in classic Mac OS because it's unique to bundles, which
didn't exist then.
Interesting. This doesn't explain though the problem met with
Entourage, which is not a bundle, yet the application file name is
"Microsoft Entourage" and the name to use for remote scripting is
"Entourage". What's up with that, any way for a script to figure this
out at runtime?
Steve
--
Steve Roy <email@hidden>
Personal homepage: <
http://homepage.mac.com/sroy>
Projects homepage: <
http://www.roydesign.net>
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.