Re: {IMPORTANT] README, Sawfish 1.6.0

Christopher Roy Bratusek <zanghar freenet de> writes:

> This is not gnome-panel-only, I'm using trayer as systemtray and it's
> the same. with any dock/panel/tray, but you're guess may be right.

True; I can reproduce it with trayer, with the viewport changes.  And it
seems to be semi-random, as you'd expect if it were dependent on the
order in which management is assumed.  If I have several maximized
windows and restart some overlap trayer and some do not.

I don't really understand the process by which windows are taken over by
sawfish, though.  Can anyone provide a primer and/or pointers?

 - What are the lisp entry points for assuming management of a new
   window?  Does it differ at all if it's a new window started while
   sawfish has been running vs a window being taken over while sawfish
   is starting?  Somehow maximize-window is being called, but I'm not
   sure where.

 - Is there any way on the lisp side to know if a window is being added
   as part of a group (e.g., at startup) or a singleton?

It seems to me that (assuming I'm right about the source of the problem)
the best thing to do would be to queue up maximizations to be done only
after sawfish knows about all extant windows.  This could be done by
adding something to after-initialization-hook or something like that.

Jeremy Hankins <nowan nowan org>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]