Xojo Conferences
MBSOct2019CologneDE

Making apps recordable - aedt resource? (Real Studio network user group Mailinglist archive)

Back to the thread list
Previous thread: Re: Serial Stuff (Solved)
Next thread: Examine Folder


FFT on an audio track   -   Wright, Tim
  Making apps recordable - aedt resource?   -   Frank Bitterlich
   Re: Making apps recordable - aedt resource?   -   Patrick Wynne
    Re: Making apps recordable - aedt resource?   -   Dean Davis
     Re: Making apps recordable - aedt resource?   -   Frank Bitterlich
     Re: Making apps recordable - aedt resource?   -   Norman Palardy

Making apps recordable - aedt resource?
Date: 28.08.02 14:25 (Wed, 28 Aug 2002 15:25:49 +0200)
From: Frank Bitterlich
Hi list,

in "REALbasic Monthly", issue 6/1999, Dan Vanderkam writes that you need
to put a "aedt" (AppleEvent Dispatch Table) into your app (in addition
to the aete resource) to make it recordable.

I have found that my apps only need a aete resource to be recordable.
What is the deal with these aedt rerources? What do they do?

I would be glad if anybody could share some details on that so that I
don't have to digest another whole volume of "Inside Macintosh".

Thanks!
Frank+++

Re: Making apps recordable - aedt resource?
Date: 28.08.02 20:43 (Wed, 28 Aug 2002 12:43:47 -0700 (PDT))
From: Patrick Wynne
IIRC, the 'aedt' resource was developed for MacApp or PowerPlant and is
used to load in a table of which events your app can handle so that the
proper handler dispatching can be set up.

In other words, you don't need to worry about it. :)

Patrick

--- Frank Bitterlich <<email address removed>> wrote:
> Hi list,
>
> in "REALbasic Monthly", issue 6/1999, Dan Vanderkam writes that you
> need to put a "aedt" (AppleEvent Dispatch Table) into your app (in
> addition to the aete resource) to make it recordable.
>
> I have found that my apps only need a aete resource to be recordable.
> What is the deal with these aedt rerources? What do they do?
>
> I would be glad if anybody could share some details on that so that I
> don't have to digest another whole volume of "Inside Macintosh".
>
> Thanks!
> Frank+++
>
> --
> Günter Schmidt & Co. oHG
> Frank Bitterlich eMail: <email address removed>
> Schlosserstr. 2-4 WWW: http://www.gsco.de/gsco
> D-60322 Frankfurt Tel.: 069 / 156809-29
> GERMANY Fax: 069 / 156809-28
>
> ---
> Subscribe to the digest:
> <mailto:<email address removed>>
> Unsubscribe:
> <mailto:<email address removed>>

=DaPatrick Wynne
<http://home.earthlink.net/~patwynne/>

=?Da
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

---
Subscribe to the digest:
<mailto:<email address removed>>
Unsubscribe:
<mailto:<email address removed>>

Re: Making apps recordable - aedt resource?
Date: 28.08.02 21:03 (Wed, 28 Aug 2002 13:03:10 -0700 (PDT))
From: Dean Davis
I may be off-base here but I believe to make an app
recordable all you need to do is send yourself events
and respond to them.

For instance, if the user chooses "New Document" from
your "File" menu, in response your code creates an
AppleEvent and sends it to itself. Then in your
AppleEventHandler you execute the function that
creates a new document in response to the AppleEvent.

In essence your program has no idea if the "New
Document" command came from the user choosing a menu
item or the user using AppleScript to issue a command.

Please correct me if I'm wrong.

Dean Davis

--- Patrick Wynne <<email address removed>> wrote:
> IIRC, the 'aedt' resource was developed for MacApp
> or PowerPlant and is
> used to load in a table of which events your app can
> handle so that the
> proper handler dispatching can be set up.
>
> In other words, you don't need to worry about it. :)
>
> Patrick
>
> --- Frank Bitterlich <<email address removed>> wrote:
> > Hi list,
> >
> > in "REALbasic Monthly", issue 6/1999, Dan
> Vanderkam writes that you
> > need to put a "aedt" (AppleEvent Dispatch Table)
> into your app (in
> > addition to the aete resource) to make it
> recordable.
> >
> > I have found that my apps only need a aete
> resource to be recordable.
> > What is the deal with these aedt rerources? What
> do they do?
> >
> > I would be glad if anybody could share some
> details on that so that I
> > don't have to digest another whole volume of
> "Inside Macintosh".
> >
> > Thanks!
> > Frank+++
> >
> >
> > --
> > Günter Schmidt & Co. oHG
> > Frank Bitterlich eMail:
> <email address removed>
> > Schlosserstr. 2-4 WWW:
> http://www.gsco.de/gsco
> > D-60322 Frankfurt Tel.: 069 /
> 156809-29
> > GERMANY Fax: 069 /
> 156809-28
> >
> > ---
> > Subscribe to the digest:
> >
> <mailto:<email address removed>>
> > Unsubscribe:
> > <mailto:<email address removed>>
> =GD=> Patrick Wynne
> <http://home.earthlink.net/~patwynne/>
> =D >
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Finance - Get real-time stock quotes
> http://finance.yahoo.com
>
> ---
> Subscribe to the digest:
> <mailto:<email address removed>>
> Unsubscribe:
> <mailto:<email address removed>>

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

---
Subscribe to the digest:
<mailto:<email address removed>>
Unsubscribe:
<mailto:<email address removed>>

Re: Making apps recordable - aedt resource?
Date: 28.08.02 21:24 (Wed, 28 Aug 2002 22:24:19 +0200)
From: Frank Bitterlich
Dean,

that's only half of it. If you do that, the ScriptEditor would never
know the terminolofy to use; after all, you're just sending an
AppleEvent to yourself. For example, if you send an event class 'MYap',
event ID 'COOL' to yourself - how should the script editor know that it
should record

tell application "MyApplication"
DoSomeCoolThing
end tell

??? That's what the 'aete' (AppleEvent Terminology Extension) is for.

Cheers,
Frank+++

Dean Davis wrote:
>
> I may be off-base here but I believe to make an app
> recordable all you need to do is send yourself events
> and respond to them.
>
> For instance, if the user chooses "New Document" from
> your "File" menu, in response your code creates an
> AppleEvent and sends it to itself. Then in your
> AppleEventHandler you execute the function that
> creates a new document in response to the AppleEvent.
>
> In essence your program has no idea if the "New
> Document" command came from the user choosing a menu
> item or the user using AppleScript to issue a command.
>
> Please correct me if I'm wrong.

Re: Making apps recordable - aedt resource?
Date: 29.08.02 03:11 (Wed, 28 Aug 2002 20:11:12 -0600)
From: Norman Palardy
You are precisely right

On Wednesday, August 28, 2002, at 02:03 PM, Dean Davis wrote:

> I may be off-base here but I believe to make an app
> recordable all you need to do is send yourself events
> and respond to them.
>
> For instance, if the user chooses "New Document" from
> your "File" menu, in response your code creates an
> AppleEvent and sends it to itself. Then in your
> AppleEventHandler you execute the function that
> creates a new document in response to the AppleEvent.
>
> In essence your program has no idea if the "New
> Document" command came from the user choosing a menu
> item or the user using AppleScript to issue a command.
>
> Please correct me if I'm wrong.

---
Subscribe to the digest:
<mailto:<email address removed>>
Unsubscribe:
<mailto:<email address removed>>