• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Calling an application
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Calling an application


  • Subject: Re: Calling an application
  • From: JollyRoger <email@hidden>
  • Date: Mon, 12 Feb 2001 10:21:28 -0600

on 2/12/2001 9:25 AM, Andrew Wylie at email@hidden wrote:

> On Sun, 11 Feb 2001 17:25:56 -0600 JollyRoger wrote
>
>> You have to admit this is a strange place to store applications. Why are
>> you storing apps on desktops other than the startup disk? And why would you
>> not move the app to a better location to solve this problem?
>>
> a)yes

Good. We're getting somewhere.

> b)I recall mentioning storing

Huh?

> c)I'm not user x on machine x running script x, why do children flush their
> toys down the toilet? Is this a bug with toilets, toys or both?

Your kid shouldn't be flush toys down the toilet. Slap him on the hand next
time and tell him not to do that.

>> Now move that script to another machine, and watch it break (display the
>> "Where is app?" dialog). :)
>>
> A .1% chance with AS1.3+ according to a Andy Bachorski in the aforementioned
> Sourcebook piece.

You mean at the top of this page?
http://www.applescriptsourcebook.com/tips/tellbyvariable.html

I think Andy is exaggerating there. My experience tells me it's more like a
90% chance that things will work out when specifying the creator.

>> Then I hate to be the bearer of bad news; but you are going to have to heed
>> our advice, and stop being so hard headed. ;) Some of us (including me)
>> have been distributing scripts world-wide for years, and know what works,
>> and what doesn't.
>>
> What advice might that be?

To use the methods we are talking about?

> I have a explanation from Marc and an ambiguous
> hint from Emmanuel, the former is interesting and the latter perplexing,
> neither seem heed able.

Instead of arguing with people, ask questions if you do not understand it
fully. Try it, it works.

> I'm sure you know plenty from your experience but you've demonstrated you
> don't know everything "what doesn't".

That sentence doesn't make sense. "what doesn't" what?

I never claimed to know everything. But I do claim to know more than you do
on this particular subject. What I know is based on a couple years
experience with scripts running on Macs word-wide using the methods we are
talking about. By contrast, what you "know" is a collection of things you
have read on web pages. Big difference.

Look, you either want help, or you don't. If you don't, then do everyone a
favor and stop this argumentative thread (or I will).

>> If you are looking for an apology for it being nasty, don't look here - I
>> didn't make it that way - but I know it's the only thing that really works
>> for distributed scripts. :)
>>
> I was looking for a yeah.

Ok. Yeah.

>> I won't bother trying to teach you why double-tell partially works, because
>> it only partially works, and you do seem to want something that works in all
>> situations.
>>
> I sought comment on the pros and cons of 2 methods.

Double-tell
Pros:
Easy to implement
Cons:
Not effective in all situations

Raw event code
Pros:
Effective in all situations
Cons:
Harder to implement

>> If you want a complete solution that will never present the "Where is app?"
>> dialog, you're going to have to use the raw event code method. If you are
>> interested in learning how to do that, just say so, and someone will show
>> you.
>
> Is there more than one raw event method?

Not that I am aware of, but I could be wrong. There is only one that *I*
use.

>>> I've since read Bill's informative Sourcebook piece on the
>>> subject and summise the only good reason to use double (or triple) tell with
>>> AS 1.3+ is if you want to avoid some undesirable launch behavior in the
>>> target app.
>>
>> It's "surmise". And you have surmised incorrectly. The double-tell serves to
>> prevent/circumvent the "Where is app?" dialog in the most popular situations
>> - but not in all situations.
>>
> a)thanks, I'd not seen the word written until now and assumed I knew it's
> spelling.

No prob.

> b)Pros and cons of 2 methods which fit that description remember. I
> stick with the surmise.

What? Please say again, that didn't make much sense.

>> Just a note: You may not be aware of this, but you come across as being
>> slightly hell-bent on rebuking what people "in the know" are telling you -
>> that's not going to get you very far here.
>> JR
>
> I was kinda hoping for some AS advice. Do you think I come across to people
> "in the know" like that too?

Not as much as the former, no.


  • Follow-Ups:
    • Re: Calling an application
      • From: Paul Berkowitz <email@hidden>
References: 
 >Re: Calling an application (From: Andrew Wylie <email@hidden>)

  • Prev by Date: Re: Calling an application
  • Next by Date: Re: Netscape preferences
  • Previous by thread: Re: Calling an application
  • Next by thread: Re: Calling an application
  • Index(es):
    • Date
    • Thread