Karl H. Beckers
2008-May-26 08:56 UTC
[compiz] Why does gdk_window_get_frame_extents give me different results on compiz vs. metacity?
Hi all, I'm trying to do some window positioning for a GTK window. I compute positions based on current window sizes and that works well under metacity using gdk_window_get_frame_extents. Under compiz positioning is all off, because that function yields different results with windows decorations being the same (gnome window decorator etc.). With mc I get a height of 67, with compiz of 43 which very much sounds like the height without decorations. Is there a good reason for this to be like that? Should GDK be smarter, or should GDK have to bother? Does compiz break a contract here? TIA, Karl.
Dennis Kasprzyk
2008-May-26 09:33 UTC
[compiz] Why does gdk_window_get_frame_extents give me different results on compiz vs. metacity?
Am Montag 26 Mai 2008 10:56:29 schrieb Karl H. Beckers:> Hi all, > > I'm trying to do some window positioning for a GTK window. I compute > positions based on current window sizes and that works well under > metacity using gdk_window_get_frame_extents. > > Under compiz positioning is all off, because that function yields > different results with windows decorations being the same (gnome window > decorator etc.). > > With mc I get a height of 67, with compiz of 43 which very much sounds > like the height without decorations. > > Is there a good reason for this to be like that? Should GDK be smarter, > or should GDK have to bother? Does compiz break a contract here? > > TIA, > > Karl. >This is a bug in GDK and the fixes are waiting for a review in their bugzilla. Dennis