Path: utzoo!attcan!uunet!samsung!usc!apple!agate!darkstar!ssyx.ucsc.edu!sirkm
From: sirkm@ssyx.ucsc.edu (Greg Anderson)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: the Ask command
Message-ID: <4253@darkstar.ucsc.edu>
Date: 9 Jun 90 21:56:37 GMT
References: <12142@june.cs.washington.edu> <4120@darkstar.ucsc.edu> <72@sun13.scri.fsu.edu>
Sender: usenet@darkstar.ucsc.edu
Reply-To: sirkm@ssyx.ucsc.edu (Greg Anderson)
Organization: UC Santa Cruz; Division of Social Sciences
Lines: 25

In article <72@sun13.scri.fsu.edu> pepke@gw.scri.fsu.edu (Eric Pepke) writes:
>In article <4120@darkstar.ucsc.edu> I write:
>> It would not be difficult to modify my XFCN so that pressing "Cancel"
>> returns the string litteral "Cancel" instead of empty.
>
>One could pass the cancel string in the invocation of the XFCN.  Then it 
>would be up to the caller to use a string that would be an inappropriate 
>answer for the particular question.  A truly paranoid caller might build 
>the string from characters that cannot be typed.

A most excellent idea.  Also:

	put "a bunch of option characters" & the ticks into cancelstring

... would insure that the user could not 'forge' a cancel even if he knew
how the stack was written.  This is, of course, overkill, as the idea is not
to prevent the user from forging a cancel, but to distinguish a cancel from
useful input.

If no one makes this mod right away, I'll do it after I graduate.  (One more
week...)
  ___\    /___               Greg Anderson              ___\    /___ 
  \   \  /   /         Social Sciences Computing        \   \  /   /
   \  /\/\  /    University of California, Santa Cruz    \  /\/\  /
    \/    \/              sirkm@ssyx.ucsc.edu             \/    \/