Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!think!ames!ucbcad!ucbvax!decvax!decwrl!sun!cmcmanis From: cmcmanis@sun.uucp (Chuck McManis) Newsgroups: comp.sys.amiga Subject: Re: my previous "Re: statement" Message-ID: <10461@sun.uucp> Date: Mon, 15-Dec-86 17:16:03 EST Article-I.D.: sun.10461 Posted: Mon Dec 15 17:16:03 1986 Date-Received: Wed, 17-Dec-86 04:35:03 EST References: <1108@spice.cs.cmu.edu> Distribution: net Organization: Sun Microsystems, Inc. Lines: 26 Mike Portuesi writes : .>Change the icon definition so that the icon contains a template of the .>allowable syntax for the command. If the command has entirely .>optional parameters, the command just executes if clicked on with the .>"Open" option or if double-clicked. If the command has required .>parameters, the Workbench throws up a requestor box and waits for the .>user to enter the necessary info. A side effect of this is that the .>requestor automatically gives the user the syntax of the command. I would suggest that all of you Amiga developers take a look at the above suggestion and consider it as an enhancement suggestion to your applications. I know lattice makes it easy to check to see if you have started from the workbench (argc == 0) it would then be a simple matter of having your option parsing code throw up a requester to get any options it needs. Additionally, if the options are optional (hmmm, you know what I mean) you could check the Tooltypes for a flag GETOPT that would indicate to your task that you should always get options from the user. -- --Chuck McManis uucp: {anywhere}!sun!cmcmanis BIX: cmcmanis ARPAnet: cmcmanis@sun.com These opinions are my own and no one elses, but you knew that didn't you.