On an embedded device I have Wayland and Weston working fine with my
touchscreen. After calibration I am able to use apps such as
weston-simple-touch but Qt 5 using Wayland doesn't recognize any touch inputs
(connecting a mouse works fine).
To fix my Qt 5 (QtWayland) issue I switched to using t
The approach taken here is to move all the stuff that belongs in a binary,
such as the main(), module and backend loading, config handling, to
a weston.c/h, keeping the behavior untouched.
All .so modules include weston.h, so they cannot be directly used by other
users of libweston, instead the mod
It seems people got a bit caught up on the words "undefined behavior" here,
especially as the very similar "undefined surface contents" appears in
wl_surface.destroy / wl_surface.release. Let's try this again, with a
different word.
Any behavior that is not explicitly defined is illegal behavior.
On Fri, 15 Aug 2014 10:11:59 -0700
Jason Ekstrand wrote:
> On Fri, Aug 15, 2014 at 12:18 AM, Pekka Paalanen
> wrote:
>
> > On Thu, 14 Aug 2014 11:31:27 -0700
> > Jason Ekstrand wrote:
> >
> > > I think the better thing to do would be to clarify the protocol to say
> > how
> > > it should be u
