It is happening with both weston and weston-launch. Do you know if the
multi touch input should work? Is it a problem in my configuration?
El 01/06/2014 03:38, "Boyan Ding" escribió:
> If you're using weston-launch there may be a problem somewhere -- I'm
> not an expert in that. But I know there'
If you're using weston-launch there may be a problem somewhere -- I'm
not an expert in that. But I know there're some backends (e.g. nested
wayland) which doesn't support touch at all at present.
On Sun, 2014-06-01 at 03:24 +0100, José Expósito wrote:
> Thank you for the quick answer.
> It happens
Thank you for the quick answer.
It happens if I run Weston as X client (weston command) or using
weston-launch.
I'm not sure how can I check the backend...
El 01/06/2014 02:50, "Boyan Ding" escribió:
> Which backend are you running on?
>
> On Sun, 2014-06-01 at 02:03 +0100, José Expósito wrote:
Which backend are you running on?
On Sun, 2014-06-01 at 02:03 +0100, José Expósito wrote:
> Hi all,
>
>
> I'm running a very simple QML multitouch example using
> MultiPointTouchArea, that works (more or less) on X11, here is the
> code:
>
>
> Rectangle {
> width: 400; height: 400
Hi all,
I'm running a very simple QML multitouch example using MultiPointTouchArea,
that works (more or less) on X11, here is the code:
Rectangle {
width: 400; height: 400
MultiPointTouchArea {
anchors.fill: parent
touchPoints: [ TouchPoint { id: point1
