After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 315647 - GdkWindowState should include fields for _NET_WM_STATE_MAXIMIZED_VERT and _NET_WM_STATE_MAXIMIZED_HORZ
GdkWindowState should include fields for _NET_WM_STATE_MAXIMIZED_VERT and _NE...
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Widget: Other
2.8.x
Other All
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 380651 650557
 
 
Reported: 2005-09-09 15:34 UTC by Thomas Fitzsimmons
Modified: 2014-03-13 05:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Thomas Fitzsimmons 2005-09-09 15:34:42 UTC 
Please describe the problem:
The AWT's Frame API supports MAXIMIZED_HORIZ and MAXIMIZED_VERT window states. 
I'd like to be able to support these states on the GTK peers.

I tried getting these properties directly from the X window using
XGetWindowProperty, within the window-state-event callback, but that produced
crashes on some window managers (see
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23558).


Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Owen Taylor 2005-09-09 17:19:38 UTC 
I think there is no good application use case for these, and the AWT
will have to deal with systems that don't support the concept anyways.
Comment 2 Thomas Fitzsimmons 2005-09-10 16:56:34 UTC 
OK, is it possible to retrieve these hints (from Xlib directly) safely from
within the window-state-event callback?  The way I was doing it before seems is
unsafe on some window managers:

XGetWindowProperty (GDK_DISPLAY_XDISPLAY (display), 
                    GDK_WINDOW_XID (widget->window),
                    gdk_x11_get_xatom_by_name_for_display (display,
"_NET_WM_STATE"),
                    0, G_MAXLONG, False, XA_ATOM, &type, &format, &atom_count,
                    &bytes_after, alu.gu_extents);
Comment 3 Kai Willadsen 2006-12-04 21:17:10 UTC 
Metacity now supports horizontal and vertical maximisation, and remembering these states seems like perfectly sensible behaviour for an application. Any chance of reconsidering the "no good application use case"?
Comment 4 Julien Olivier 2011-06-10 08:58:22 UTC 
Without that, it's impossible to solve bug #650557, and the same bug that's going to be opened for other applications.
Comment 5 Matthias Clasen 2014-03-13 05:10:33 UTC 
I consider this addressed with GDK_WINDOW_STATE_TILED