Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!csd4.milw.wisc.edu!leah!albanycs!crdgw1!uunet!mcvax!ukc!tcdcs!csvax1!ecarroll
From: ecarroll@csvax1.cs.tcd.ie (Eddy Carroll)
Newsgroups: comp.sys.amiga
Subject: Re: Using IconX on Projector?
Message-ID: <48208@csvax1.cs.tcd.ie>
Date: 15 Jun 89 21:33:04 GMT
References: <2147@hp-sdd.hp.com>
Organization: Computer Science Department, Trinity College Dublin
Lines: 24

In article <2147@hp-sdd.hp.com>, tony@hp-sdd.hp.com (Tony Parkhurst) writes:
>     I thought IconX was supposed to work on any program that could run from
> the CLI.  It seems that I can't get some to work.  For example, when I run
> Projector from an IconX script, IconX opens the window, projector seems to
> start, but then it hangs.  Any ideas?  In the script file, I use the exact
> same command that I use from the CLI.

The problem is that IconX doesn't simulate a CLI completely (in fairness,
duplicating the CLI environment exactly takes a heck of a lot of work!).
So, while IconX will work with most programs, it won't work with them all.

The easy solution is to setup two scripts, say script.1 and script.2.
Script.1 has the usual IconX-type icon associated with it (set WINDOW=NIL: in
the icon Info tooltypes to prevent the usual IconX window from being opened
unnecessarily), and contains NEWCLI CON:50/50/540/100/XICON FROM SCRIPT.2.
Script.2 doesn't need an icon. It contains all the CLI commands you want to
execute. Add an ENDCLI command at the end, to make sure the window goes
away.

I've used this method several times, and I haven't found any problems with it.
-- 
Eddy Carroll               ----* Genuine MUD Wizard  | "You haven't lived until
INTER: ecarroll@cs.tcd.ie                            |    you've died in MUD!"
 UUCP: {..uunet}!mcvax!ukc!cs.tcd.ie!csvax1!ecarroll |  -- Richard Bartle