On 2018-05-17 1:14 PM, Daniel Stone wrote:
> That's fine, but we would have to look at the trade-off: they would
> have to drop functionality they use, in exchange for something which
> is worse for them.
I guess I don't fully understand why it's worse for them. It should be
functionally equivale
Hi Drew,
On 17 May 2018 at 13:11, Drew DeVault wrote:
> On 2018-05-15 3:01 PM, Olivier Fourdan wrote:
>> FWIW, both SDL and Xwayland uses “persistent” and we have working
>> implementations of the protocol in weston/libweston and mutter, so it might
>> be hard to convince people (both compositor
On 2018-05-15 3:01 PM, Olivier Fourdan wrote:
> FWIW, both SDL and Xwayland uses “persistent” and we have working
> implementations of the protocol in weston/libweston and mutter, so it might
> be hard to convince people (both compositor and clients developers) to drop
> their working implementati
Hi,
On Tue, May 15, 2018 at 2:36 PM, wrote:
> Hi again,
>
> Yes I propose removing the persistent lifetime, removing the concept of
> different lifetimes as a whole, and just keeping the oneshot lifetime as
> the implicit lifetime.
>
> I initially did not consider any of the race conditions, but
Hi again,
Yes I propose removing the persistent lifetime, removing the concept of
different lifetimes as a whole, and just keeping the oneshot lifetime as the
implicit lifetime.
I initially did not consider any of the race conditions, but even then, I do
not think it justifies the complex pers
Hi,
On Thu, May 3, 2018 at 10:53 PM, wrote:
> I propose removing the concept of persistent pointer constraints and
> lifetimes in the pointer constraints protocol.
>
> This would vastly simplify the implementation of the protocol in the
> compositor, but slightly increase the complexity in the c
I propose removing the concept of persistent pointer constraints and lifetimes
in the pointer constraints protocol.
This would vastly simplify the implementation of the protocol in the
compositor, but slightly increase the complexity in the client.
Benefits:
The compositor wouldn't have to kee
