[vlc-devel] [PATCH 1/4] libvlc: Add "fullscreen-monitor" setting
ajanni at videolabs.io
Wed Oct 16 20:46:26 CEST 2019
Sorry if this wasn't clear in the previous post.
I mean, you're making review on an UX patch (vlc-variable and usage in Qt), so
it seems sensical to me that it has to match the expected UX.
I'm not against the API at all, I find it well designed too, but I don't think
you can have a well designed API, non-generic variable for outputs and the UX
for the user in VLC at the same time. The UX seems an unavoidable part of what
we're achieving for VLC 4, because we design for use case. And I'd better keep
the well designed API than the non-generic variable. Maybe I'm wrong but
absolutely nothing came against the questions I raised.
My arguments are on the previous-previous post, but the TL;DR is: how the
interface can determine what configuration variable to set in the general way ?
On Wed, Oct 16, 2019 at 09:35:22PM +0300, Rémi Denis-Courmont wrote:
> Le keskiviikkona 16. lokakuuta 2019, 0.56.31 EEST Alexandre Janniaux a écrit :
> > Hi,
> > The fact that you want the vout window out of the vout thread tend to tell
> > me the opposite, and you wrote about it in previous mails, but it doesn't
> > really matter. The point is what you didn't quote from the previous mail:
> > what you expect from this API, from an UX point of view,
> This API is designed according to how lower layers typically expose this: you
> can either go windowed, go fullscreen without specifying the monitor, or go
> full screen on one monitor out of a list of them.
> I don't know why you want to bring the UX here. I don't really see how there
> is a problem, but if there is, we are not in a position to change how
> windowing systems work for the sake of some VLC UX anyway.
> Реми Дёни-Курмон
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
More information about the vlc-devel