Hi,
We are using Weston Wayland based compositing for our solution, though we are
able to render image, video text etc.
We are using x11 backend along with desktop shell to build the solution which
requires rendering of multiple media contents (image, videos etc) together. We
are using followi
There are 4 possible cases why a touchpad suspends right now: lid switch,
tablet mode switch, sendevents disabled and sendevents disabled when an
external mouse is present.
But these reasons can stack up, e.g. a lid switch may happen while send events
is disabled, disabling one should not re-enabl
Because we register the handler separately (once for lid, once for
tablet-mode) the handler is called twice for the same event. This causes a
double-suspend of the touchpad, though it doesn't seem to have any real
effect.
Split it up so that each handler function only does one thing.
Signed-off-b
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
