• 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: App Supplied Coercion?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: App Supplied Coercion?


  • Subject: Re: App Supplied Coercion?
  • From: Ehsan Saffari <email@hidden>
  • Date: Fri, 3 Aug 2001 06:07:26 -0600

On Thu, 2 Aug 2001 22:53, Jon Pugh <email@hidden> commanded:

>At 9:12 PM -0600 8/2/2001, Ehsan Saffari wrote:
>>Thanks. I am interested in finding the coercions without launching every
>>app or checking the docs. Is there a programmatic method for finding
>>these coercions?
>
>You can't do it without launching the app, since there are no required
>resources necessary. You can do it all from code.
>
>That said, there's an aeinfo dcmd for Macsbug which dumps the AE handler
>(and coercion) tables. This is probably the easiest solution. You can
>call AEGetCoercionHandler to get the address of the handler, for all the
>good that does. ;)
>
>The aeinfo dcmd is here: http://www.merzwaren.com/snippets/

Thanks Jon, but as much as I enjoy messing with Macsbug ;) I was looking
for a method to find the coercions by AS, turns out AkuaSweets does it:

the installed coercions: Get a list of the currently installed coercions.
the installed coercions in the system area/in the application area

cheers
ehsan


  • Prev by Date: Stack overflow error
  • Next by Date: Re: Speech impediment
  • Previous by thread: Re: App Supplied Coercion?
  • Next by thread: Remoing the resource fork
  • Index(es):
    • Date
    • Thread