Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hplabs!hp-pcd!hpcvlo!asd
From: asd@hpcvlo.HP.COM (Alesia Duncombe)
Newsgroups: comp.windows.x
Subject: Xtoolkit pop-up questions
Message-ID: <3940046@hpcvlo.HP.COM>
Date: Fri, 20-Nov-87 18:27:07 EST
Article-I.D.: hpcvlo.3940046
Posted: Fri Nov 20 18:27:07 1987
Date-Received: Mon, 23-Nov-87 03:48:40 EST
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 23


I am going through the new Xtoolkit documentation and am please to see 
the new information on shells.  I am not sure if the new design contains
everything that we need and will not be certain until we have worked with
the new bits.

I do have a couple of questions regarding the pop-ups.

   The routines XtCallbackNone, XtCallbackNonexclusive and
   XtCallbackExclusive appear to be useful except that it states
   that the widget that executed the callback list is set 
   insensitive.  Maybe in some specific cases this would be 
   useful but I question whether this is generally useful.  
   Is this necessary?

   The spring-loaded pop-ups are defined to be pop-ups that are
   brought up with a mouse button press and taken down by a mouse
   button release.  I assume that this is primarily for interacting
   with a pop-up menu.  Again, I would argue that this is a specific
   case of a pop-up menu.  The menu selection model may be to bring
   up the menu on a mouse button press and take down the menu on 
   another button press.  Why is the spring-loaded distinction
   necessary?