Re: <<event FNDRsope>> (WAS Re: Path to app ...)
Re: <<event FNDRsope>> (WAS Re: Path to app ...)
- Subject: Re: <<event FNDRsope>> (WAS Re: Path to app ...)
- From: John W Baxter <email@hidden>
- Date: Tue, 4 Dec 2001 22:06:45 -0800
At 14:21 -0800 12/4/2001, Christopher Nebel wrote:
>
On Tuesday, December 4, 2001, at 04:01 AM, Nigel Garvey wrote:
>
>
> <<event FNDRsope>> and the Finder's 'open' work in exactly the same
>
> way - though I suppose there must be a difference as the former doesn't
>
> compile to the latter.
>
>
If memory serves, <<event FNDRsope>> is the old "open selection" event
>
from back when the Finder didn't have a real object model. (Apparently,
>
it can take an explicit thing to open -- try it without any parameters
>
and see what happens.) It's been obsolete for some time, and the Mac OS
>
X Finder doesn't support it. I'd suggest using "open" instead.
Close...it's the open event from the archaic Finder.
It has to be led kicking and screaming to the things to open: you give it
the containing folder AND an alias (or list) for the thing(s) to open. Pay
no attention to the information in the alias which tells Finder what the
containing folder is, (or to the man behind the curtain ;-)).
In archaic Finder's defense, the world changed after it was finalized for
System 7. And a darn good thing it is, too: aside from oddities like that
"it's in here and here it is" parameter pair (used in many of the events,
that Finder declined to send replies: "just tell me what to do and don't
worry about it...I may or may not get around to it".
--John (who hadn't opened Frontier 3.0 for a LONG time until researching
this)