OSD above fullscreen windows

Martin Gräßlin mgraesslin at kde.org
Thu Aug 14 11:11:47 UTC 2014


On Thursday 14 August 2014 12:01:41 Thomas Pfeiffer wrote:
> On Thursday 14 August 2014 11:49:21 Martin Gräßlin wrote:
> > On Thursday 14 August 2014 11:40:43 Thomas Pfeiffer wrote:
> > > On Tuesday 12 August 2014 15:58:13 Marco Martin wrote:
> > > > On Tuesday 12 August 2014, Aleix Pol wrote:
> > > > > > Looking at my TVs, it always shows the "OSD" when volume changes,
> > > > > > that
> > > > > > would
> > > > > > be something I'd also expect a media center to do.
> > > > > 
> > > > > Maybe we want different OSD when fullscreen. I've never seen a TV
> > > > > with
> > > > > the
> > > > > volume information on the center.
> > > > 
> > > > and this would cause problems exactly in ... ?
> > > 
> > > I agree that showing the OSD in the center of the screen while watching
> > > a
> > > video would be rather annoying. There's a reason why most TVs put their
> > > OSDs on the edge of the screen.
> > > But as has been said, the Look & Feel of the PMC shell can take care of
> > > that.
> > 
> > on the other hand it also shows why I think that showing notifications
> > relevant during a fullscreen window is active, must be in the
> > responsibility of the application. Only the video player can know where
> > the black bars are to place the OSD.
> 
> See Martin K.'s argument: People are more likely to use the dedicated volume
> keys on their keyboards rather than shortcuts to change volume in the
> application, so they are changing the master volume, not the application
> volume. If we could ensure that all video players would catch changes in
> masdter volume when full screen and display their own OSD instead of
> Plasma's, that would surely be great, but I don't know if that's even
> possible let alone realistic.

I did not necessarily mean that it's the application's task to handle it. I 
meant: we need communication. The application must provide us information 
whether
a) it handles it itself (we don't want two volume changed OSDs)
b) where we can safely put the OSD

Cheers
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140814/98c804a1/attachment.sig>


More information about the Plasma-devel mailing list