accepting-values (:own-window t) in clim 2

• To: jmorrill@BBN.COM, clim@BBN.COM
• Subject: accepting-values (:own-window t) in clim 2
• From: Scott McKay <SWM@stony-brook.scrc.symbolics.com>
• Date: Mon, 14 Sep 1992 18:41-0400
• In-Reply-To: <464.716502306@bbn.com>
• Supersedes: <19920914221053.0.SWM@SUMMER.SCRC.Symbolics.COM>

    Date: Mon, 14 Sep 1992 16:25 EDT
    From: Jeff Morrill <jmorrill@BBN.COM>


    I think it would be useful if accepting-values (:own-window t)
    could be run at a time when *application-frame* was NIL (or unbound or
    whatever) and *query-io* (et. al.) was not a clim stream.

    This corresponds to a state where the only clim stream is
    in the AVV frame.

    In clim 1 I open a root window so that AVV will get
    a stream that it can deal with.

    (let ((stream *query-io*))
      (when (not (clim:extended-output-stream-p stream))
	(setq stream (..find or open a root window..)))
      (accepting-values (stream :own-window t)
	...))

    The clim 2 spec says that if the stream is T then the value
    of *query-io* is used.  It would be nice if clim would check
    *query-io* and at the very least complain that it is not
    a "suitable stream," and better yet, it would look
    at *default-server-path* and just work.

    If there is some reason why clim can't work that way, then I
    would like to know how I can construct a "suitable stream"
    as I do for clim 1.

It will "just work" in CLIM 2.0.  That is,

  (accepting-values ('any-darned-thing :own-window t) ...)

will pop up an own-window AVV using the current frame manager on the
default port.

0,,

• accepting-values (:own-window t) in clim 2
• From: Jeff Morrill <jmorrill@BBN.COM>

• Prev: accepting-values (:own-window t) in clim 2
• Next: [naha@riverside.scrc.symbolics.com: CLIM Listener]
• Index: CLIM Mailing list (1-Sep-92 to 31-Dec-92)
• Thread: CLIM Mailing list Index (1-Sep-92 to 31-Dec-92)