> > BUTTON -> script which does a CALL "SCRIPTNAME" "ARGUMENT" -> YOUR SCRIPT
> > 
> >  So  you have many small "call scripts" to call the needed one and all with
> > a single difference in the ARGUMENT parameter of the CALL command.
> > 
> >  Ciao,
> >    Giuseppe Chillemi
> 
> Thanks for the advice, but those are the fashions I resent using. I do it
> the "argument" way right now, but was wondering if there was a way to
> determine the button since that would ease the process of adding buttons,
> etc.
> 
> Perhaps include some kind of IDs for buttons? 

Optional IDs for buttons would be no big problem. If an ID for a
button would have been defined, it could be automatically sent as
argument to the script. 

> And text?
 
Do you think of text fields? I see no real use for IDs for such
fields, as they cannot start any action at all.

--
Nils Bandener          ///
nils@dinoex.sub.org  \XX/    http://www.amigaworld.com/support/fiasco/
nilsb@amigaworld.com