Re: frame auto-unmaximized

[Stephen J. Turnbull]

Sam Steingold writes:
 > On Mon, Jul 6, 2009 at 11:00 AM, Jan Djärv<address@hidden> wrote:
 > > Sam Steingold skrev:
 > >>
 > >> with the current cvs head under gnome:
 > >> emacs -q
 > >> click on the "maximize" button (upper right corner, 2nd from right).
 > >> the emacs frame is maximized.
 > >> C-M-<right> to go to the next workspace
 > >> C-M-<left> to go back to the emacs workspace
 > >> observe that the emacs frame is no longer maximized.
 > >> I hope this is not the intended behavior!
 > >>
 > >
 > > No, it sounds like a bug.  Are you using metacity or something else (compiz
 > > perhaps)?
 > 
 > metacity.

Metacity doesn't bother to remember that *it* maximized the app (the
app of course has no power to do so), and so happily fullfils a
request from the app to return to its natural size.  I forget the
details, but this is a particular behavior of metacity and KDE's
default WM; other WMs do remember that they've maximized the window
and refuse future requests unless they come from the user.

I think it's more in line with user expectations if the WM remembers,
but evidently Havoc thinks differently.

I believe that there is a way for the WM to differentiate between a
request by a program that is obeying an explicit command from the user
to request a window configuration, and a program that is simply making
a request based on widget resources.  The WM of course should respect
the former, and ignore the latter if it has its own mandate from the
user.  Again I forget the details, but it may be that metacity ignores
this difference.