Re: _NET: Disabling shading

[Dominik Vogt <dominik vogt gmx de>]

On Wed, Oct 01, 2003 at 01:30:15PM +0200, Lubos Lunak wrote:
> On Wednesday 01 of October 2003 12:24, Denis O. Mikhalkin wrote:
> > On Wed, 2003-10-01 at 13:32, Lubos Lunak wrote:
> > There is a need for more grained specification, and applications usually
> > DO have more complex modality states in design, they just unable to
> > implement them. There are at least three kinds which people usually
> > request from Java - parent-wide, group-wide, application-wide. On
> > Windows, there is also system-wide. So there is at least four kinds
> > known.
> 
>  Aha, I have never seen this myself. Is there some document or application 
> which I could have a look at to see the difference?
> 
> >
> > >  On the other hand, I wouldn't mind extending WM_TRANSIENT_FOR to be able
> > > to point to more than one window, as I actually recently encountered a
> > > problem related to this WM_TRANSIENT_FOR limitation. I'll try to write a
> > > patch for the spec and post it.
> >
> > I would really like to not extend WM_TRANSIENT_FOR anymore and to
> > introduce some special property related to this. WM_TRANSIENT_FOR has
> > been designed to serve other purposes.
> 
>  As far as I know, WM_TRANSIENT_FOR is usually understood as "this is my 
> main/superior window". In which case wouldn't this be good enough for modal 
> dialogs?

I don't think any change is necessary.  Using a "locally active"
focus policy would allow the application to control focus within
its own windows, and no application must be allowed to take
control over the whole desktop.

Ciao

Dominik ^_^  ^_^