[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: Motif FAQ (Part 3 of 9)
Previous Document: 63) Why is XtGetValues of XmNx and XmNy of my toplevel shell wrong?
Next Document: 65) How can my application know when the user has quit Mwm?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: Motif FAQ (Part 3 of 9)
Previous Document: 63) Why is XtGetValues of XmNx and XmNy of my toplevel shell wrong?
Next Document: 65) How can my application know when the user has quit Mwm?
64) How do I get XmNx and XmNy positions to be honored correctly?
[Last modified: Nov 96] Answer: One answer is to pass the right hints to the window manager, perhaps using XSetWMNormalHints. Another approach comes from Shane Burgess (shane@radionics.com) who writes: By setting the XmNdefaultPosition resource (on XmBulletinBoard or its subclasses, including the message dialogs) to False, I've found that all my XmNx & XmNy requests gets set correctly. Pete Sakalaukus (sakalauk@pelican.st.usm.edu) says that XmNdefaultPosition only works with olwm, not mwm.
Top Document: Motif FAQ (Part 3 of 9)
Previous Document: 63) Why is XtGetValues of XmNx and XmNy of my toplevel shell wrong?
Next Document: 65) How can my application know when the user has quit Mwm?
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
kenton@rahul.net (Ken Lee)
Last Update July 25 2008 @ 00:12 AM