Re: Tell Launcher to quit
Re: Tell Launcher to quit
- Subject: Re: Tell Launcher to quit
- From: Chris Nebel <email@hidden>
- Date: Sun, 24 Dec 2000 12:10:49 -0800
- Organization: Apple Computer, Inc.
>
Chris Nebel - do you care to comment? Or Cal?
Oh, ecch. I'd been assuming this was a problem with the Finder, but it's
actually a problem with AppleScript. Here's what's going on (I think):
First off, Launcher hasn't changed for quite some time, and is still an old-world
"cdev" control panel, as opposed to the applications-in-all-but-type "APPC"
control panels like Memory or Mouse. Used to be, "cdev" control panels were
actually managed by the Finder -- they ran inside the Finder's context, they'd
show up in its window list, etc. -- which is why Mr. Haesler's stunt worked,
bizarre as it might look. It wasn't a bug, it was working as designed.
In Mac OS 9, this changed: cdevs now get a process all to themselves. (Did you
notice that Launcher started showing up in the application menu as a separate
item in Mac OS 9? The other irritating side effect for me -- yes, I use Launcher
-- was that clicking on the desktop would no longer bring it to the foreground.)
At first I thought that there was a problem with the cdev shell not accepting
events, but then I realized that AppleScript wasn't even trying to send it any.
The real problem (I'm fairly certain) is that AppleScript thinks it knows what an
application looks like and will check before sending it any events, and a cdev
like Launcher doesn't look like what it expects -- it has the wrong type, and
lacks any "CODE" or "cfrg" resources, which are the normal marks of an
executable.
Anyway, I've filed a bug. It shouldn't be too hard to fix, so I'll see if we can
get it into our next update.
--Chris Nebel
AppleScript Engineering