Re: _NET_WM_ALLOWED_ACTIONS

[Carsten Haitzler (The Rasterman) <raster rasterman com>]

On Tue, 21 Nov 2006 12:33:16 +0100 Lubos Lunak <l lunak suse cz> babbled:

> On Tuesday 21 November 2006 09:21, Oleg Sukhodolsky wrote:
> > On 11/20/06, Lubos Lunak <l lunak suse cz> wrote:
> > > On Monday 20 November 2006 15:01, Havoc Pennington wrote:
> > > > Oleg Sukhodolsky wrote:
> > > > > Hello,
> > > > >
> > > > > Is there any _standard_ way to disable the Minimize (or Maximize, or
> > > > > Close, whatever) menuitem on the system menu (accessible via
> > > > > Alt-Spacebar or Alt-RightClick under Metacity)?
> > > > > I've read the _NET_WM_ALLOWED_ACTIONS spec, but it's not clear
> > > > > whether this is client- or WM- managed hint...
> > > >
> > > > It is WM-managed; to disable things like that I think you have to use
> > > > the old MWM hints.
> > >
> > >  Assuming the WM gives a damn about those. Hints are just that, hints and
> ...
> > That's exactly true! However, I implement somewhat like a splash screen,
> > and I don't wanna use the _NET_WM_WINDOW_TYPE_SPLASH window type as it
> > makes the splash window being "always on top" under metacity. And I
> > don't want the window to be "override redirect" as well.
> 
>  So, in other words, if I'm getting it right, you're saying that you want to 
> work around the window manager? Been there, done that, still suffering a lot 
> from it. And you even want a standard for that.
> 
> > In this scenario, I can't tell the metacity not to show the menu when
> > the user performs Alt-RightClick, on the other hand I have to disable
> > the menu items I mentioned before. That's why I'd like to implement such
> > a behavior. Does anyone have any ideas how?  Of course it would be
> > better to have code which works with (almost) all WMs, i.e. use
> > something from standard ;)
> 
>  What I think you actually really want is to a) complain to Metacity 
> developers that their handling of TYPE_SPLASH is insufficient b) send them a 
> patch c) use a WM that handles it better.

indeed. working around 1 wm simply means int he end other wms with differing
policies will suffer more as your solution works for 1 then royally falls apart
in a spectacular fashion on other wm's. my pet hate for doing this has ben
java's x layer in the past. it's royally stupid and coded to assume all the
wrong things and tries to work around specific wm's (i sat down and read the
awt window code and almost puked).

it causes nothing but trouble and these days if anyone says "java apps don't
work right..." i just ignore the message. i don't even read further.

please don't create another "java". don't work around wm's - you start with
one, then have to work around another, then another, and another - then a new
wm appears and you have to work around that too. simply live with it - if you
don't PERSONALLY like it - change WM's :) your users are also free to do so.

> -- 
> Lubos Lunak
> KDE developer
> --------------------------------------------------------------
> SUSE LINUX, s.r.o.   e-mail: l lunak suse cz , l lunak kde org
> Lihovarska 1060/12   tel: +420 284 028 972
> 190 00 Prague 9      fax: +420 284 028 951
> Czech Republic       http//www.suse.cz
> _______________________________________________
> wm-spec-list mailing list
> wm-spec-list gnome org
> http://mail.gnome.org/mailman/listinfo/wm-spec-list
> 


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    raster rasterman com
裸好多
Tokyo, Japan (東京 日本)