CompuServe Thread

#Arexx & Icons

3 messages in this thread
#18849From: Ken CooperJan 9, 1992 2:24 AM
I have a problem getting an icon to do a job (guess you can tell that I have been mucking with wb2.04 :). I also installed Wshell v2.0. The program in question is DiskMaster v2.0 and it has arexx controls and a port called 'DM'. Normally I work out of wshell window. I've made a simple Arexx script (called DMup.rexx) that first checks to see whether DiskMaster's port is available, else – run DiskMaster. Sometimes in the wild frenzy of computing, a second Diskmaster gets started, not that it wouldn't run, but it's a waste of good memory for no good reason, hence DMup.rexx. From there it gets alias'd to 'dm' for short, making it easy to type at the prompt. Now, after going thru the Wshell manual, I find an item called 'AppWindows'. Neat stuff. Okay, so I add a line in the icon information window in Tool Types: WSHAPP="DMup & *N" So when I pick up the icon and drop in the wshell, the arexx program runs and I get DiskMaster – one way or the other. I also want the option of double clicking the icon, to also start this arexx script. I assume the Default Tool should be: c:rx – or should it be ":c/rx" – or just "rx" ? Besides having the WSHAPP line from above, as one of the Tool Types, what can I add as tool types, that will start this particular arexx progam by double clicking? Ken Cooper – Vancouver
#18859From: Bill HawesJan 9, 1992 7:42 AM
Ken, On AmigaDOS 2.0 systems, the RX program is normally in the SYS:rexxc directory. Make sure you're using the right path for the default tool in your icon. -Bill Hawes
#18910From: John BianchiJan 10, 1992 11:26 PM
Ken, In 2.0, the path set up before the LOADWB command in the S-S sets up SYS:RexxC in your system path (if not just add a path command to your S:User-StartUp Anyway, under 2.04, the system path is searched for ToolType entries. No more need to provide the path (ie: ToolType rx will work). Remember, only the path setup before the LOADWB will be used by WorkBench as later PATH <> ADD commands on a CLI will only be used for that CLI. It really is a bother to remove the path stuff, especially when a PD author expects ":c/MuchMore" when I put MuchMore in my DH0:Readers directory and add it to my command path in s:User-StartUp (I keep C: as CBM supplied only files). When LIST and DIR can handle multiple assigns, then my special dirs will be also be assigned to C: as in: Assign C: SYS:C DH0:MyC … but alas, many progs including CBM's LIST only see SYS:C. Guess it'll have to be fixed in 2.1 or something