From: Tony H. <h...@re...> - 2004-08-12 22:29:43
|
In <200...@ho...>, Jonatan Liljedahl wrote: > On Wed, 11 Aug 2004 22:21:41 +0100 > Tony Houghton <h...@re...> wrote: > > > In <200...@ho...>, Jonatan Liljedahl wrote: > > > > > But the other stuff seems to work, one detail about the > > > above_state-stuff only: When right clicking on the sticky-button to > > > turn above off, it shouldn't lower the window imho... Is the > > > right-click also interpreted as a titlebar right-click (lower > > > window) perhaps? > > > > No, I think it's where I wanted automatic raising and lowering when > > _NET_WM_STATE_ABOVE and _BELOW change, and I think they use the same > > function as the sticky-right-click. I tend to agree with you, so I'll > > see if I can improve it. > > When net_wm_state_above is set, the window should rise of course, but > when it's unset I don't think it should be lowered. And same thing for > _below, it should lower when set but when _below is removed it shouldn't > automagically raise. Is it that simple though? For simplicity I'll just talk about the _below state, but the same applies in reverse for _above. If the state is removed, the window shouldn't be raised right to the front, true, but what if it was below another _below window? Shouldn't it now be raised above that? That could be done by manipulating client_list_stacking as in clientRaiseForce, but if it has any transients they'll make it a bit more fiddly. -- TH * http://www.realh.co.uk |