On 5/12/2011 7:28 PM, Denis Lila wrote:
Hi Denis.
we could use implementation for them as a default one and skip it in
case if custom querying is not needed.
I'm not sure what you mean by this. Can you please ellaborate,
or possibly give a short pseudocode example?
I think Denis F. meant to say that the correct way to add support for
mutter or any other window manager is to get rid of the workaround and
fix this missing ConfigureNotify issue, so we don't have to query for
particular WM at all.
Thanks,
Artem
Thank you,
Denis.
----- Original Message -----
Hi Denis,
the fix looks good but may be we should consider another approach.
Instead of going through just all known WMs like we do under the
switch
729 switch (XWM.getWMID()) {
730 case XWM.CDE_WM:
731 case XWM.MOTIF_WM:
732 case XWM.METACITY_WM:
733 case XWM.SAWFISH_WM:
734 case XWM.MUTTER_WM:
If you investigate a possibility and efficiency of such a change it
would be great.
Thank you,
Denis.
On 10.05.2011 17:48, Denis Lila wrote:
Hi.
We have this bug where, using the mutter window manager,
if one moves netbeans anywhere on the screen except at
the top left and then maximizes it, clicking is broken.
This is because after maximizing the position of the
XDecoratedPeer is not updated. On Metacity and some other
WMs this is done using a WM specific workaround.
I've added Mutter as a WM, and this webrev fixes the problem:
http://icedtea.classpath.org/~dlila/webrevs/mutterBug/
Any comments are much appreciated.
Thank you,
Denis.
