Executing actions within the same thread
The
do_actions_of,
do_drop_in_actions_of,
do_menu_actions_of,
and
source
commands execute the specified actions within the same thread,
rather than in a separate thread.
You might want to do this to keep control over the order in which
the actions are executed.
For example, the following script sends the
example myprint trigger, below,
to a sequence of icons in the
variable $*:
for i in $*
do
do_actions_of myprint $i
done
Because a do_actions_of command is used,
each myprint action executes and completes
before the next one is started.
NOTE:
Because the action commands are executed in the same thread,
changing a local variable in the trigger action for
myprint will affect local variables in the current thread.
Generally this is not a problem because only loop variables
will be used in both scripts, and these are protected.
See also:
-
do_actions_of,
do_drop_in_actions_of,
do_menu_actions_of,
and
source
in the
deskcommands(XC)
manual page
Next topic:
Signals
Previous topic:
Pipelines
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 26 May 2005