Re: Addressing an app that may or may not exists (without alerting user)
Re: Addressing an app that may or may not exists (without alerting user)
- Subject: Re: Addressing an app that may or may not exists (without alerting user)
- From: "John C. Welch" <email@hidden>
- Date: Mon, 13 Mar 2006 08:56:05 -0600
- Thread-topic: Addressing an app that may or may not exists (without alerting user)
On 3/13/06 03:50, "Sean P. Kane" <email@hidden> wrote:
> In the end I could not get any of the suggested methods to work. Even
> if I had logic that should have missed the tell application block
> completely if they did not have Growl installed, it still seemed to
> ask for it (and I tried 4 or five methods), so for now, I just made
> it a requirement, instead of an option. This is broken functionality
> in my opinion. There should be a proper way of handling this
> situation. I can't imagine that it is all that unusual.
Why not just search for it ahead of time? Not in the main script, but create
a stub script that only looks for growl. If it finds it, it starts the
"growlified" script and quits itself. If it doesn't, it starts another
script and quits itself. Since you're supporting Growl, you're pretty much
locked to a version of the OS that will support script bundles, so just use
multiple scripts in the bundle, running the most appropriate one based on
the situation.
--
Q: Doctor, how many autopsies have you performed on dead people?
A: All my autopsies are performed on dead people.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden