Re: 1.9d

[Tim Janik <timj gtk org>]

On Thu, 23 Dec 1999, Marko Macek wrote:

> Tim Janik wrote:
> > > >also the 0xFFFFFFFF is superfluous (besides obviously hackish), this is
> > > >exactly what _NET_WM_STATE_STICKY is meant to indicate.
> > >
> > > Not true - 'sticky' indicates that the window should not move when moving the
> > > viewport. 'Desktop 0xffffffff' indicates that the window should appear on all
> > > desktops.
> > 
> > so you want to distinguish between viewport-scrollable sticky windows and screen
> > sticky windows? can you give an example where this is actually usefull?
> 
> I am not sure about that. I don't care much about viewport scrolling.
>  
> > and why don't we have _NET_WM_STATE_STICKY and _NET_WM_STATE_SCROLLABLE_STICKY
> > to indicate this then (with one state taking precedence over the other)?
> > (_NET_WM_DESKTOP is still the wrong place for this, since for both sticky
> > behaviours, _NET_WM_DESKTOP is a meaningless property).
> 
> Having "occupy all desktops" just a simple value for _NET_WM_DESKTOP
> makes perfect sense to me.

you mean "use 0xFFFFFFFF to indicate occupying all desktops when scrolling,
contain a bogus value for unscrollable occupation of all desktops otherwise",
which doesn't at all make sense to me.
furthermore for window managers that do not implement scrollable desktops
(viewports) a window has to be considered sticky if it is flaged as such
with _NET_WM_STATE_STICKY *or* contains 0xFFFFFFFF in _NET_WM_DESKTOP.
so i'm going to slightly alter my idea and suggest:

"_NET_WM_DESKTOP

_NET_WM_DESKTOP <desktop>, CARDINAL/32

Cardinal to determine the desktop the window is in (or wants to be) starting
with 0 for the first desktop. A Client would usually not set this property,
in which case the Window Manager can place it according to its placement
policies.
The Window Manager SHOULD honor _NET_WM_DESKTOP whenever a withdrawn window
requests to be mapped. When being in another state (iconified or mapped), a
Pager may request a change by sending a _NET_WM_DESKTOP client message to the
root window, where window is the respective window, type _NET_WM_DESKTOP,
format 32, l[0]=<desktop>. The Window Manager MUST keep this property updated
on all windows.
This property should not be considered at all meaningfull for clients flagged
as _NET_WM_STATE_STICKY in their _NET_WM_STATE property."

and:

"_NET_WM_STATE

_NET_WM_STATE, ATOM[]

A list of hints describing the window state.
[...]
Possible atoms are:
_NET_WM_STATE_MODAL, ATOM
_NET_WM_STATE_STICKY, ATOM
_NET_WM_STATE_STICKY_SCROLLABLE, ATOM
_NET_WM_STATE_MAXIMIZED_VERT, ATOM
_NET_WM_STATE_MAXIMIZED_HORZ, ATOM
_NET_WM_STATE_SHADED, ATOM
_NET_WM_STATE_SKIP_TASKBAR, ATOM
[...]
_NET_WM_STATE_STICKY indicates that a window SHOULD have a fixed position on
the screen, even when the virtual desktop scrolls.

_NET_WM_STATE_STICKY_SCROLLABLE indicates that a window when flagged with
_NET_WM_STATE_STICKY may be scrolled with the current viewport, if the Window
Manager implements viewport scrolling.
[...]"


> 
> Mark
> -- 

---
ciaoTJ