AFAICT upstream did not implement window-state events for the Quartz backend of GTK2 -> Inkscape's test for maximized window state "fails" if compiled with GTK+/Quartz. Thus the window information is saved "incorrectly" (with full dimensions of maximized window and unset 'maximized' state) in <namedview> and the document window cannot be unmaximized via window manager (the user instead has to manually resize it by dragging the edges/corners). The window state event works as expected with X11 backend though (tested with attached pygtk script [1] for both available backends (X11, Quartz) of GTK+ 2.24.30).
AFAICT upstream did not implement window-state events for the Quartz backend of GTK2 -> Inkscape's test for maximized window state "fails" if compiled with GTK+/Quartz. Thus the window information is saved "incorrectly" (with full dimensions of maximized window and unset 'maximized' state) in <namedview> and the document window cannot be unmaximized via window manager (the user instead has to manually resize it by dragging the edges/corners). The window state event works as expected with X11 backend though (tested with attached pygtk script [1] for both available backends (X11, Quartz) of GTK+ 2.24.30).
-- /developer. gnome.org/ pygtk/stable/ class-gdkevent. html#id2914311
[1] pygtk docs:
https:/