Re: App Supplied Coercion?
Re: App Supplied Coercion?
- Subject: Re: App Supplied Coercion?
- From: Paul Berkowitz <email@hidden>
- Date: Thu, 02 Aug 2001 08:49:17 -0700
On 8/2/01 3:17 AM, "Ehsan Saffari" <email@hidden> wrote:
>
Hi
>
>
In various AS sources it is pointed out that applications, as well as
>
osaxen, may provide coercions. Anyone know of an application that does
>
so? Finder maybe? And if an app does do it, how does one go about finding
>
out what coercions are provided, any particular resource to check?
>
As far as I can see, all applications which implement the 'save' command
from the Standard Suite - and which incorrectly and improperly state 'in
[alias]' as the class type for the 'in' parameter in their Dictionaries
except for a few new OS X apps (TextEdit, Mail and OmniWeb) which correctly
state 'in [string]' - are in fact coercing 'string' to 'file specification'.
It's pretty clear that the incorrect '[alias]' terminology must have been
taken from a faulty Apple SDK, and which Apple has at last corrected in some
of their new apps for OS X - perhaps even in a new SDK too since OmniWeb has
got it right. (Some of the Apple OS X apps, such as QuickTime 5, still have
it wrong). But I'm quite interested in understanding what sort of coercion
is actually taking place - it certainly _looks_ like a
string-to-file-specification coercion. Can Chris Nebel or anyone else (Jon
Pugh?) explain?
--
Paul Berkowitz