#AREXX
4 messages in this thread
To anyone who can help:
I can't seem to get my ToasterPaint AREXX programs to work, specifically, the
action codes that will actually get it to "do something." Both my programs
and the samples included with TP don't work. When I TRACE any of these
programs, the action codes produce no errors, but worse yet, no action! Also,
identical functions from the included samples produce syntax errors
when copied into my own AREXX programs but not in their original files.
Are you running these from ToasterPaint or outside of it? Most programs with
ARexx ports which use their own arexx scripts need the scripts be run from
inside the program itself. Check your TP manual about using arexx scripts to
determine how they are to be used. They may need to have an arexx port opened,
which only opens when the program runs.
The documentation (a text file in the TP ARexx directory) says that the ARexx
programs should be run OUTSIDE while TP is loaded, like in CLI, where commands
to TP are sent by enclosing them in single quotes (e.g., 'Lo24'). Of course, I
also tried to get them to work while INSIDE TP "just in case," but that
produced similar results – nothing! Do you think it matters that I'm accessing
TP via the switcher function SWITCHER(STTP)?
Still stumped,
BJ
Bizhan,
Well, it's always tough to debug something like this remotely and
without something similar with which to experiment. I read a couple of other
responses, so I know I'm probably repeating another message. You might check
to be sure that the scripts are addressing the correct command port. Usually,
but not always, when an ARexx script is run from outside of a program then the
program's arexx commands need to be sent to the correct host. That is usually
done with the ARexx command ADDRESS portname. If the script is run from within
the program which is being controlled, the program usually handles that, if
written correctly. If the port address is being called in the ARexx script,
but nothing is happening, then it's possible that the program's ARexx port
isn't open. You can check that by reading the program docs to see what the
default ARexx port is named. Then from the CLI you can type 'say
show("P","portname")' which should result in a return of 1 if the port is found
or 0 if the port wasn't found. The quotes should be exactly as I typed them.
If the port is there, then check the ARexx script to be sure that
ADDRESS portname is there and that it has the correct name for the program's
ARexx port.
I'm sorry, but I'm not familiear with Switcher, so I don't know what to
tell you.