Path: utzoo!attcan!uunet!wuarchive!brutus.cs.uiuc.edu!apple!bloom-beacon!EXPO.LCS.MIT.EDU!kit From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) Newsgroups: comp.windows.x Subject: Re: Questions on popups. Message-ID: <8908241900.AA29986@expo.lcs.mit.edu> Date: 24 Aug 89 19:00:53 GMT References: Sender: daemon@bloom-beacon.MIT.EDU Organization: The Internet Lines: 39 > I am still not clear why one needs to use XtTranslateCoords() > routine? Why can't one use x_toot and y_root values (instead of x and y > values) from event->xbutton structure? If you want to implement a true popup menu, this method will be fine. XtTranslateCoords() is needed if you want to pop up your menu relative to something else (e.g. a pull-down menu). > Some of the athena widgets have 'actions' [such as set(), > highlight()] listed for them. Are there any such actions for shell > widgets? (Looks as if MenuPopup() and MenuPopdown() are.) Are there any other? Nope. > (Looks as if MenuPopup() and MenuPopdown() are.) Are there any other? Nope, these are global actions that can be used with any widget. They are not shell actions. > ...the button A never gets a 'LeaveWindow' event... > ...how can I program this to avoid the "problem"? This is an instrinsics mis-feature, and will be fixed in R4. > "X Toolkit Warning: Pop-up menu creation is only supported on ButtonPress or > EnterNotify events." > What does this mean? It means that popuping up your menus using MenuPopup() is not supported on an enter-window event. You must use a button or keypress event with menu popup. It looks like the error message is incorrect. Chris D. Peterson MIT X Consortium Net: kit@expo.lcs.mit.edu Phone: (617) 253 - 9608 Address: MIT - Room NE43-213