Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!ucsd!rutgers!uwvax!astroatc!nicmad!hill From: hill@nicmad.UUCP (Ray Hill) Newsgroups: comp.windows.x Subject: Re: Chicken or Egg Xtk Problem Message-ID: <2952@nicmad.UUCP> Date: 1 Aug 88 21:27:34 GMT References: <2926@nicmad.UUCP> <9740044@hpfclp.SDE.HP.COM> Organization: Nicolet Instruments, Biomedical Division Lines: 45 In article <9740044@hpfclp.SDE.HP.COM>, diamant@hpfclp.SDE.HP.COM (John Diamant) writes: > > 2. Is there anyway to move a "transient shell" widget after it has been > > realized? (or popped up once?) > > Yes, there should be. You should be able to use XtMoveWidget. The X Toolkit Intrinsics Documentation for X11.2 on page 69 seems to be saying that XtMoveWidget should only be called by the parent of the widget. It also says that "Clients that wish to change the geometry of a widget should call XtSetValues ..." Using XtSetValues has no affect after the transient widget has been mapped once. > What window manager are you using? X11.2 release of "uwm". > If it is a reparenting window manager, the problem is > most likely a change in the conventions having to do with changing hints > versus configure. I don't think so. > If you want to prove this is what is happening, see what happens when you > try to move an overrideShell window instead (don't leave the dialog box that > way, but test it out). This change made no difference. > John Diamant > Software Development Environments > Hewlett-Packard Co. ARPA Internet: diamant@hpfclp.sde.hp.com > Fort Collins, CO UUCP: {hplabs,hpfcla}!hpfclp!diamant Well, even though the docs told me not to, I called XtMoveWidget. And guess what, it works. However, one must not to call "XtMoveWidget" in place of XtSetValues in all cases. Thanks for the help John. I'm posting this to see if there is a more correct way. Or is this the right way the docs are wrong (or I'm reading them wrong). I'd hate to have to re-write my code after a switch to X11.3 or a different platform. Ray Hill hill@nicmad