NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/comp/windows/openloo/3294

Internet Message Format | 1992-07-30 | 1.8 KB

Path: sparky!uunet!tdat!swf
From: [e-mail] (Stanley Friesen)
Newsgroups: comp.windows.open-look
Subject: Re: Xview popup problem
Message-ID: <[e-mail]>
Date: 30 Jul 92 19:18:25 GMT
References: <[e-mail]>
Sender: [e-mail]
Reply-To: [e-mail] (Stanley Friesen)
Organization: NCR Teradata Database Business Unit
Lines: 34

In article <[e-mail]> [e-mail] (Vidiot) writes:
|
|I am encountering some difficulty working around one of the "features"
|of XView. Does anyone know how to get around the following?
|
|I create a popup window with its pushpin out. When ever a button is pressed,
|the popup *always* disappears, even if I explicitly set the XV_SHOW attribute
|for the frame to TRUE in the notify proc for the button, before the return
|to the Notifier. ...

That's right.  That is how it is supposed to work.  The blessed way of
doing what you want is described in the XView Reference Manual as follows:

   If the panel item is part of an unpinned command frame, then the window
   is dismissed if PANEL_NOTIFY_STATUS is XV_OK.  If PANEL_NOTIFY_STATUS is
   set to XV_ERROR, then the window is not dismissed.
and later:
   Default: XV_OK

Thus for those buttons that do not finish the operation of the you must
*always* set PANEL_NOTIFY_STATUS to XV_ERROR, as follows:
    xv_set(item, PANEL_NOTIFY_STATUS, XV_ERROR, 0);
(where item is probably the first arg to your callback function).


Yeah, I know, it really isn't an *error*, but you have to say it is.
(This is one thing that OLIT got better - in that toolkit the pop-up
panel is divided into two regions, and upper region contining non-finishing
items, and a lower region that contains the items that should complete
the pop-up operation).
--
[e-mail]            (formerly tdatirv!sarima)
  or
[e-mail]