Suggest approach to accepting-values dialog

• To: curt@eraserhead.jpl.nasa.gov
• Subject: Suggest approach to accepting-values dialog
• From: Scott McKay <swm@harlequin.com>
• Date: Tue, 24 May 94 15:08:10 EDT
• Cc: clim@BBN.COM
• In-Reply-To: Curt Eggemeyer's message of Tue, 17 May 1994 08:03:07 -0700 <199405171503.IAA06895@eraserhead.Jpl.Nasa.Gov>

   Date: Tue, 17 May 1994 08:03:07 -0700
   From: Curt Eggemeyer <curt@eraserhead.jpl.nasa.gov>

   In Clim2.0 land, when you use the :own-window t option in accepting-values,
   does clim automatically generate a new window each time it is called, or
   is it smart enough to reuse one previously generated?

   In my particular application, I have a very extensive accepting-values
   dialog (could have a hundred or more accepts) that is used fairly often
   and in the old clim1.1 scheme used a separate pane layout to bring it to
   the forefront when the user wanted to "tweak" an object. Now, I would like
   to have it pop up as a tied-in window to the application frame.
   Any suggestions on what is the best way to implementate this (ala my own
   make-pane or make-clim-application-pane, of which I'm not sure how to tie
   in with my application frame)?

Did anyone answer this?

I would make this its own application frame with an :ACCEPT-VALUE pane
in it, and then simply use ENABLE-FRAME/DISABLE-FRAME to show/hide the
frame.  Make this app have an external interface to initialize the
state of the queries.

• Prev: frame-top-level-process
• Next: a display goodie...
• Index: CLIM Mailing list (1-Jun-94 to 30-Jun-95)
• Thread: CLIM Mailing list Index (1-Jun-94 to 30-Jun-95)