accepting-values recursively

• To: curt@eraserhead.jpl.nasa.gov
• Subject: accepting-values recursively
• From: "John G. Aspinall" <JGA@alderaan.scrc.symbolics.com>
• Date: Fri, 13 Mar 1992 15:59-0500
• Cc: clim@BBN.COM
• In-Reply-To: <9203131752.AA05852@eraserhead.Jpl.Nasa.Gov>

SWM and KAnderson each make good suggestions about breaking up large
dialogs.  There's another point that people are missing, I think.  

The semantics of nested accepting-values isn't defined.  I'd like to
see a description of the behaviour that is desired.

(Practically speaking, accepting-values is a loop that runs repeatedly
until you exit.  User code specifies the appearance of the display.  If
you put anything in the display part of the loop *other than accepts and
buttons* (which are treated specially) that asks for input, then you are
asking the display phase to pause, unfinished, while you do something
else.  That, to my mind, breaks the contract of the (outer) accepting
values.)

Note: I'm referring to accepting-values simply nested within other
accepting-values, not to accepting-values within buttons within
accepting-values as SWM was proposing.

• accepting-values recursively
• From: Curt Eggemeyer <curt@eraserhead.jpl.nasa.gov>

• Prev: CLIM 1.1 from Lucid
• Next: Rotated Text?
• Index: CLIM Mailing list (1-Jan-92 to 31-Aug-92)
• Thread: CLIM Mailing list Index (1-Jan-92 to 31-Aug-92)