asd@hpcvlo.HP.COM (Alesia Duncombe) (11/21/87)
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?
asd@hpcvlo.HP.COM (Alesia Duncombe) (11/21/87)
I omitted one last comment. The MenuPopup function defined seems to be a very specific function. First, it is unusual that the translation manager be aware of a particular action. Second, it is specifically defined for ButtonPress and EnterWindow. There appears to be no reason to limit it to these actions other than the function, as is defined, solves a specific need. Again, I would like to see this solve the general problem. Alesia Duncombe HP X-ray Team