Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!deccrl!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!edcastle!cs.ed.ac.uk!gdmr From: gdmr@cs.ed.ac.uk (George Ross) Newsgroups: comp.windows.x.motif Subject: Re: interactive placement of pop-ups & precendence of main app window Message-ID: <8721@skye.cs.ed.ac.uk> Date: 11 Apr 91 11:11:16 GMT References: <12110005@hpfcbig.SDE.HP.COM> Sender: nnews@cs.ed.ac.uk Reply-To: gdmr@cs.ed.ac.uk (George Ross) Organization: Department of Computer Science, Edinburgh University Lines: 22 In article <12110005@hpfcbig.SDE.HP.COM>, koff@hpfcbig.SDE.HP.COM (Caroline Koff) writes: > Try setting the XmNdefaultPosition to False when you create the dialog > boxes, as in XtSetArg(args[i], XmNdefaultPosition, False). Then to > position your dialog boxes on your own, use XtMoveWidget call. > From Asente & Swick chapter 4, page 204 (at the "warning hand"): "The only way for an application to request a geometry change for a widget is to issue an XtSetValues call setting some of the geometry resources. This is very important to remember. Other methods of changing geometry exist in the toolkit, but they are for use either by parents to change the geometry of their children or for a widget instance to request a change in its own geometry. Unfortunately, the Intrinsics cannot enforce this. If you ever find yourself using anything other than XtSetValues to control a widget's geometry from within an application, you have made a programming error, and the widgets are likely to become corrupted." -- George D M Ross, Department of Computer Science, University of Edinburgh Kings Buildings, Mayfield Road, Edinburgh, Scotland, EH9 3JZ Tel: 031-650 5147 Internet: gdmr@cs.ed.ac.uk JANET: gdmr@uk.ac.ed.cs