Open GoogleCodeExporter opened 8 years ago
Unfloating and then floating the window again sets its size back properly, so
the bug happens only when the window is first created.
Original comment by ein...@gmail.com
on 18 Oct 2010 at 8:33
Doesn't happens for me with winecfg and a 3 monitor setup (1x 16:10, 2x 4:3)
But I have the same problem with opera when I install it with gtk. Does winecfg
use gtk? Then it would be a generic problem with gtk and xmonad :/
Original comment by FelixBla...@gmail.com
on 18 Oct 2010 at 8:49
It happens with gcolor2 (gtk), and the same thing happens with the windows
created by OCaml graphics library (it creates windows by calling X directly,
without toolkits), but I haven't seen the issues with KDE applications, though
I don't know any similar adequate applications.
The afterwards-created floating dialog windows (various preference windows,
help-abouts etc I just tried looking at) seem to be correct both in KDE and GTK
applications.
Original comment by ein...@gmail.com
on 18 Oct 2010 at 9:14
I think the problem is that xmonad internally represents window dimensions as
fractions of screen size, and these are computed from the initial window
position and size. So, if an application creates a new window at (0,0) and then
asks the window manager to position it, xmonad computes the size as a fraction
relative to the screen containing (0,0) and then places the window on whatever
screen is currently active. If the size of this screen is different, so is the
size of the placed window.
Original comment by liskni...@gmail.com
on 19 Oct 2010 at 8:50
Yeah that could be possible.
At my problem xmonad sometimes creates a windows which is width > 5000px. My
total screen size is 4960x1600.
The problem (at me) typ. only occurs with the width, not the height.
Original comment by FelixBla...@gmail.com
on 19 Oct 2010 at 8:58
Original issue reported on code.google.com by
ein...@gmail.com
on 18 Oct 2010 at 7:16Attachments: