Nelson Minar wrote:
>But I have a related
>question - how do I *not* set the position of a window? I don't call
>any methods to set the position, yet my window manager thinks the
>window is demanding to be placed at 0,0. I'd rather let the window
>manager decide itself.
>
>Am I doing something wrong here? Is this a (small) JDK bug for X?
And Pete Wyckoff replied:
>Take a look at MComponentPeer.pInitialize(). It sets the location of
>the window (to 0,0 if no setLocation call has occurred). This is different
>from "any other application." Many window managers will honor requests
>by the application for explicit placement, overriding the default user-
>interactive placement algorithm.
>
>It looks like there's no way to avoid this when using the motif native
>AWT layer, short of hacking the window manager to notice when
>USPosition|PPosition is 0,0, and ignore it.
This bug annoys me intensely. I have my window manager (fvwm) set to allow
interactive placement of applications, but Java applications refuse to
cooperate.
For some reason Sun have listed this as a request for enhancement in the
Bug Parade (where it has bug id 4102292, and appears in the Top 25 RFEs).
The two related bug ids (4158145 and 4162290) can't be found.
I wish Sun would do something about this. I don't want my Java applications
to behave any differently from others: _all_ applciations should acknowledge
the user's window manager settings.
Ron
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
