Re: Lots of _NET_WM_STATE_FULLSCREEN issues ...

[Gerd Knorr <kraxel bytesex org>]

Forgot to Cc: the list ...

----- Forwarded message from Gerd Knorr <kraxel bytesex org> -----

Date: Thu, 13 Feb 2003 15:05:34 +0100
From: Gerd Knorr <kraxel bytesex org>
Subject: Re: Lots of _NET_WM_STATE_FULLSCREEN issues ...
To: Matthias Clasen <maclas gmx de>
Content-Type: text/plain; charset=utf-8

> >      old way:  xawtv can switch via VidMode extention.
> >      _NET_WM:  ???
> 
> I don't think switching physical resolution should be part of the EWMH. So
> you will probably have to continue to use VidMode (unless R&R offers a more
> Vendor-neutral way to achieve the same effect)

Ok.

> >  (2) Somehow related to (1).  What happens if you enter fullscreen
> >      mode with a virtual screen larger than the physical screen?
> >
> >      old way:  xawtv can check what the phyical screen size is,
> >                again using the VidMode extention, then make the
> >                window size match the physical screen.
> >      _NET_WM:  ???
> 
> I'd say that "screen" in fullscreen refers to the physical screen (ie
> monitor), not to any virtual large
> desktop implemented by the WM or the Xinerama extension.

I'm not refering to some virtual screen implemented by the window
manager.  I'm talking about virtual screens implemented by the X-Server:
You can put multiple mode lines into your XF86Config file, for example
"640x480" and "1024x748".  That will give you a 1024x740 sized screen.
You can and then switch between "640x480" and "1024x748" with Ctrl + Alt
+ plus/minus (or via VidMode extention).  If you are running with
"640x480" the X-Server will pan the display if needed.

What will happen if I switch to fullscreen mode in 640x480 ?

> The EWMH doesn't currently say anything about Xinerama (should be in a
> future version), but
> I think the current practise is to maximize/fullscreen a window not to the
> full screen, but only to
> the monitor it's currently on.

Fine.

> Look at the very bottom of
> http://www.freedesktop.org/standards/wm-spec/1.3/html/x362.html
> theres a section containing recommendations for stacking order.

Ok.  Looks like setting _NET_WM_STATE_FULLSCREEN should be enougth ...

  Gerd

-- 
Weil die späten Diskussionen nicht mal mehr den Rotwein lohnen.
				-- Wacholder in “Melanie”