emacs-devel
[Top][All Lists]
Advanced

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

Re: override_redirect of X Window System


From: Jan D.
Subject: Re: override_redirect of X Window System
Date: Wed, 24 Sep 2003 20:17:47 +0200

On Wed, 2003-09-24 at 18:14, Jan D. wrote:
It is not a metacity bug - there is an agreed upon protocol for full
screening windows, and override-redirect is not it.

http://bugzilla.gnome.org/show_bug.cgi?id=106740

This is about being able to move windows above panels for accessibility
reasons, not how apps are supposed to fullscreen.

And that is what I said.


To Kazu: I'd recommend you research the latest EWMH specification, that
will show you how to properly fullscreen windows.

This requires XSendEvent.  It is not available from elisp.
It is also not a solution that works on all window managers out there.

It works on all standards compliant WMs, which is an increasing number.
There's no need to expose XSendEvent to elisp, simply having a
fullscreen function that does the necessary machinery would work too.

The good things about standards is that there are so many to choose from :-)
Seriously, there are WMs that where created before EWMH existed.  One
is CDE, which is used a lot.  Others in use still, are fvwm 1.x, olvwm,
mwm and KDE 1.x.

If we add a solution to Emacs that says "call this function to get
fullscreen" and then it does not work on peoples WMs, I think we are
going to see bug reports.  And if there is one response I don't like
w.r.t. things that doesn't work, it is "please change your
unrelated app/version/OS... to something else".

Exposing XSendEvent can be potentially useful for more things than
fullscreen.  For example, expand vertically and/or horizontally that
are also in EWMH.

But I do not make these desicions for Emacs, these are just my opinions.
If it is descided to put in a C-function that only works on a subset of
X window WMs, I can implement it.  But I think my suggestion is more
portable and more useful (hardly surprising :-)

        Jan D.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]