Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!bellcore!snoopy!ik From: ik@snoopy.bellcore.com (Ik Su Yoo) Newsgroups: comp.windows.x.motif Subject: Re: interactive placement of pop-ups & precendence of main app window Message-ID: <1991Apr19.120541.1064@bellcore.bellcore.com> Date: 19 Apr 91 12:05:41 GMT References: <12110005@hpfcbig.SDE.HP.COM> <1991Apr16.131440.16590@hri.com> <1991Apr19.110554.13933@gibdo.engr.washington.edu> Sender: usenet@bellcore.bellcore.com (Poster of News) Reply-To: ik@ctt.bellcore.com (Ik Su Yoo) Distribution: usa Organization: Bell Communications Research Lines: 45 In article <1991Apr19.110554.13933@gibdo.engr.washington.edu>, slh@gibdo.engr.washington.edu writes: > In article <1991Apr16.131440.16590@hri.com> rudolph@sparc20.hri.com (David Rudolph) writes: > [stuff] > |When I tried setting XmNdefaultPosition to false, the window came up at > |(0,0). Since I have interactivePlacement set to True, I expected that I > |would be able to position the window with the mouse. Any ideas why this > |wasn't the case? > | > R3/Motif 1.somethingorother on AIX3.1.5/IBM RS/6000-530: > > I'm not using interactive placement and setting > XmNdefaultPosition to False doesn't give the results desired either. > I've tried all sorts of combinations, > even tried unmapping the window, managing, setting the position > and mapping, still sucks. > If the dialog is up and I try invoking it again > (with the button that activates it) it finally goes where it should, > not satisfactory. > Hmmm, maybe if you unmap it, manage it twice... > > Also so since I'm whining, I've never been able to get rid > of decorations on a toplevel at execute time. > (using mwm* resources in .Xdefaults doesn't count for this) > This has also been discussed a lot and I think I've tried > all the suggestions. > > I suppose most likely both of these things are broken... Try unmapping it and managing it twice while doing a hand stand :-) Seriously, though, I got the "right thing" to happen by not realizing the dialog's parent widget and setting XmNdefaultPosition to false. In most cases, you'd want to realize your parent widget, especially if it is the top level widget containing your main window. If this is the case, try creating a dummy application shell, never realizing it, and creating pop-up dialogs as its children. Of course, you can try other variations, too. This may be highly implementation dependent, I don't know. Ik Su Yoo RRC 1H-229, (908) 699-5764 ik@ctt.bellcore.com