Re: How to 'load' osaxen
Re: How to 'load' osaxen
- Subject: Re: How to 'load' osaxen
- From: Paul Skinner <email@hidden>
- Date: Tue, 19 Jun 2001 11:27:56 -0400
on 6/19/01 1:11 AM, Christopher Nebel wrote:
>
On Sunday, June 17, 2001, at 02:24 PM, Paul Berkowitz wrote:
>
>
> Jon Pugh has several times recommended an alternate method to
>
> restarting,
>
> which always seems to work and is less disruptive:
>
>
>
> 1. _Duplicate_ (option-drag) the osax in Scripting Additions folder to
>
> the
>
> desktop (or anywhere outside the System folder).
>
>
>
> 2. Drag the original from SA folder to the trash.
>
>
>
> 3. Empty the trash.
>
>
While this will certainly get rid of the terminology, I don't believe it
>
will disable any coercion handlers the addition defines. As we've seen
>
several times before, those are the really tricky ones to track down.
>
>
>
--Chris Nebel
Is there a method for discovering what coercions are provided by an
OSAX? A list somewhere public?
I recently got bitten by Akua when it kindly coerced text into a file
spec for me. I don't see any entries in it's dictionary that relate to this
coercion and so I began wondering what I can do to at least be aware of the
possible coercions that an OSAX performs.
I certainly can verify that I had to restart to remove the effect of the
Akua text-to-filespec coercion. Nothing short of that would stop it from
functioning.
--
Paul Skinner