amr@dukee.egr.duke.edu (Anthony M. Richardson) (12/07/90)
I'm in the process of switching to the WorkBench environment
after working in the CLI environment for several years.
I'm trying to use IconX to create icons for several scripts
that I have lying around. No problem for the most and I
stumbled into a few nifty tricks. (Did you know that if you
specify WINDOW=NIL: in the icon's TOOL TYPES then IconX's
pesky window won't appear?)
I do have a few scripts that require a file name as argument
("execute script filename"). The documentation I have for IconX
(the old, white 1.3 Enhancer manual) states:
You can work through the Workbench and use extended selection to
pass Workbench files to the script. These files appear to the script as
keywords. To use this facility, the .key keyword must be at the start
of the script. In this case, ....
Neat, I thought. So I tried an example script,
.key filename
echo "Made it to here."
echo <filename>
echo "Made it to here, too"
I attached a project icon to the script, and set the default tool to
C:iconx and set the Tool Types window appropriately. If I double
click the icon, the two messages in the script appear in the window.
However, if I use extended selection (I hold the SHIFT key down
and then click on an arbitrary icon and then double click on my
script's icon) in an attempt to pass a filename to the script,
nothing happens. Well, something happens, the sleep balloon appears
and it seems as if something is trying to run, but the window doesn't
appear and so nothing gets echoed.
So am I missing something, am I doing extended selection wrong, or what?
Email responses preferred.
Thanks in advance,
Tony Richardson amr@dukee.egr.duke.edu