Re: Proposal: client property for de-maximize geometry

[Joseph Krahn <joseph krahn gmail com>]

>> My proposal is that the WM sets _NET_WM_NORMAL_GEOMETRY whenever it
>> sets a _NET_WM_STATE flag that causes a window geometry change that
>> can be undone to restore the remembered geometry. This property would
>> be deleted whenever the WM clears the geometry-affecting state flag.
>>

It is easy to obtain the "normal" geometry simply by toggling the
relevant state flags off, querying the window geometry, then restoring
the state flags, hopefully without too much noticeable flicker. So, I
agree that it is not worth adding yet another property to manage, even
if it might occasionally be useful. The spec is already heavy on
Window Property management.

If it is ever deemed useful to make the "normal geometry", or some
other extended window information available, it would be better to
implement as a ClientMessage request, similar to
_NET_REQUEST_FRAME_EXTENTS. Then, rarely used information can still be
accessible, but without wasted property-setting overhead.

Thanks,
Joe Krahn