Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!nrl-cmf!ukma!gatech!hubcap!ncrcae!ncrlnk!uunet!mcvax!ukc!harrier.ukc.ac.uk!eagle.ukc.ac.uk!rlh2
From: rlh2@ukc.ac.uk (Richard Hesketh)
Newsgroups: comp.windows.x
Subject: Re: wrong window coordinates after uwm "Move"
Message-ID: <6190@eagle.ukc.ac.uk>
Date: 16 Dec 88 11:50:49 GMT
References: <8812141923.AA03161@dinorah.wustl.edu>
Reply-To: rlh2@ukc.ac.uk (Richard Hesketh)
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 34

In article <8812141923.AA03161@dinorah.wustl.edu> y2@DINORAH.WUSTL.EDU (Yeong-Yeong Liu) writes:
>...  Program seems worked fine until I
>repositioned the top level window to a different location by using
>"Move" function under uwm.  The popup insists on appearing at the same
>old location no matter where its ancestors are.

This certainly seems to a problem with the toolkit not being informed of an
update in the geometry of the window of the popup shell.  If you iconize the
application and then de-iconize it, any further pop ups will appear in the
right place (until moved again!).

Therefore it appears that uwm won't inform the window of a geometry change
unless it is really forced to?  This problem has been around
since R2, I assume it is being look at?

>Here is my test program which didn't work:

>
>	....
>	y = 10;
>	XtTranslateCoords(w,x,y,&x,&y);
>	XtMoveWidget(popupshell,x,y);

In R3 the XtMoveWidget call should be replaced by an XtSetValues call.
This should only be used in R2 sources due to a bug in the R3 Shell widget
which has been fixed in R3.  Only composite widget classes should make
direct calls to XtResizeWidget or XtMoveWidget, everybody else should use
XtSetValues or XtMake{Resize, Geometry}Request's.  This enforces correct
use of class built geometry handlers.

Richard Hesketh   :   rlh2@ukc.ac.uk    ..!mcvax!ukc!rlh2
---                                               
Computing Lab., University of Kent at Canterbury,
Canterbury, Kent, CT2 7NF, England.