On Mon, Feb 18, 2019 at 04:28:18PM +, Daniel Stone wrote:
> Hi Simon,
>
> On Mon, 18 Feb 2019 at 16:22, Simon Ser wrote:
> > On Friday, October 26, 2018 11:13 AM, Simon Ser wrote:
> > > Compositors also expose output refresh rate, which shouldn't be used
> > > for synchronization purposes.
Hi Simon,
On Mon, 18 Feb 2019 at 16:22, Simon Ser wrote:
> On Friday, October 26, 2018 11:13 AM, Simon Ser wrote:
> > Compositors also expose output refresh rate, which shouldn't be used
> > for synchronization purposes.
>
> I'd like to bump this patch, because people apparently do use
On Friday, October 26, 2018 11:13 AM, Simon Ser wrote:
> Compositors also expose output refresh rate, which shouldn't be used
> for synchronization purposes.
I'd like to bump this patch, because people apparently do use wl_output's
refresh rate for synchronization purposes in Firefox [1]. I
All wl_output properties don't always make sense for all
compositors.
Some compositors might not implement a "global compositor space",
(e.g. 3D compositors) in which case properties like x and y don't
make sense.
Some compositors might expose virtual outputs, in which case modes,
make and model
