Hi Tom, > > - The code for fetching the frame extents now uses the (new?) GDK > > function gdk_window_get_frame_extents() rather than pulling the frame > > extents using the extended window property _NET_FRAME_EXTENTS. > > This will result in the wrong insets being calculated upon window > realization, > since gdk_window_get_frame_extents relies on the window being mapped. For > now > you can ifdef this code based on the presence or absence of X. Ideally > though, > _NET_FRAME_EXTENTS support would be added to the X11 implementation of > gdk_window_get_frame_extents.
Not sure if I understand correctly. Window realization is when the window object is created, but not yet visible (==mapped), right? In this case, the _NET_FRAME_EXTENTS thing reports 0-extents, because it doesn't know yet about the real borders. This is exactly what gdk_window_get_frame_extents() does in this case. When the window is mapped, we receive a callback and fetch the real extents. What's the difference between _NET_FRAME_EXTENTS and gdk_window_get_frame_extents() then? /Roman -- Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org aicas Allerton Interworks Computer Automated Systems GmbH Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany http://www.aicas.com * Tel: +49-721-663 968-0 USt-Id: DE216375633, Handelsregister HRB 109481, AG Karlsruhe Geschäftsführer: Dr. James J. Hunt
