On Monday 11 August 2014 11:14:09 Martin Klapetek wrote:
> On Mon, Aug 11, 2014 at 8:48 AM, Martin Gräßlin <mgraess...@kde.org> wrote:
> > On Sunday 10 August 2014 23:23:13 Kai Uwe Broulik wrote:
> > > Hi there,
> > > 
> > > I might have missed that in the discussion but is it deliberate that the
> > 
> > OSD
> > 
> > > doesn't raise itself above fullscreen windows?
> > > 
> > > I found it uncomfortable to not have immediate feedback when changing
> > 
> > volume
> > 
> > > using keyboard during a movie.
> > 
> > Yes, that's intended:
> > http://commits.kde.org/kwin/1576c55cd2ce428e8f76bead72c3db2f8aa35ac9
> 
> Should it be? I would also expect the OSD to always be on top of active
> fullscreen windows, whatever that window might be. We also have OSD for
> changing the keyboard layout for example, not showing it in some fullscreen
> app could be quite limiting.
> 
> Can we reconsider that?

honestly: no. There's a reason for the way it is and I'm quite sure we 
discussed it. If the arguments (e.g. private chat going over presentation) do 
not apply for OSD then we have to realize that a OSD needs a dedicated window 
type with a dedicated layer. But changing notification type handling is wrong.

Cheers
Martin

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

Reply via email to