6/13/94
James:

Here are two samples of what I have done throughout my GLUE menus.

Sample 1) -User inputs 2 or 3 values per instructions so the .DO file
          can take them as arguments, using :P | | :K
         -Even if only one value is needed, the placement of it in the
          command line may not be at the END as needed for :P | | :K,
          OR there may be multiple commands using the single value

Sample 2) -This shows my problem of wanting to "trap" and test user input
         -I have the .DO file argument strategically placed in the command
          string so that it will cause AMOS to cough and choke if user
          enters anything at all; no input has to represent a confirmation
         -It works but it's gludgy!  (An IF..THEN to test a variable's
          value after user input would be marvelous)

Thanks for whatever you can come up with to help out on these, if anything.

Clive


SELECTION "Rename File on Your PC"
    HELP-MESSAGE "Reduce to 6 chars before trans"
    EXECUTE XY 5 1
    EXECUTE :<FOLLOW THESE INSTRUCTIONS|>
    EXECUTE :<~~~~~~~~~~~~~~~~~~~~~~~~~|>
    EXECUTE :<Enter ALL 3 items TOGETHER with a space between each one|>
    EXECUTE :<||Existing filename?, New filename? & PC directory where file is located?|>
    EXECUTE :<|                >
    EXECUTE :P | GLUPCR.DO |:K
    RETURN-AFTER-PAUSE

SELECTION "Complete ABC AR-GL Interface"
    EXECUTE :S | LOG DSK1:[1,2] | XY 5 1
    EXECUTE :<Proceed with interface? (RETURN for Yes) >
    EXECUTE :P | GLUABC.DO |:K
    EXECUTE :S | HOME
    EXECUTE :R |
    RETURN-AFTER-PAUSE

You are viewing proxied material from gopher.floodgap.com. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.