"running" command issues
"running" command issues
- Subject: "running" command issues
- From: Loren Ryter <email@hidden>
- Date: Sat, 05 Jul 2008 13:31:30 -0400
- Thread-topic: "running" command issues
Can anyone explain what the utility of using Leopard's "running" command is?
I was under the impression that it is faster than get "every process" from
"system events", and thought the latter was meant to be deprecated.
Unfortunately there seem to be problems. For example, try this:
set anapp to "nothing"
if application anapp is running then set isRunning to true
AppleScript will ask you to locate the application "nothing".
Obviously this is not desired behavior. I'd try to use "using terms from"
but I'm studiously avoiding that due to the know bug with compiling that on
Leopard and running on Tiger.
Is there a work around? How can you trap the situation where anapp is not
known? Can it be referred to by an application bundle ID instead of a name,
and would this make a difference?
Thanks.
_______________________________________________
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