Weston multitouch support?
Peter Hutterer
peter.hutterer at who-t.net
Tue Jun 3 03:57:27 PDT 2014
On 3/06/2014 19:43 , José Expósito wrote:
> Hi Peter,
>
> Thank you very much for your answers
>
> > there are some special rules for clickpads, specifically a click with a
> > finger resting on one of the software-button areas will produce a right
> > or middle click.
> > [...]
> > eventually yes, but not at this point. as I said in the previous
> email you
> > just won't have access to the data. I think a sensible solution here
> is to
> > have libinput send semantic events like "pinch", "rotate", etc. and then
> > have the compositor hook into those. the actual compositor part would be
> > quite small and have no actual gesture recognition, that would be done
> > inside libinput. but we're just not there yet.
>
> Is a pity that the implementation plans are these... I mean, with this
> approach the clients will not be able to implement features like smooth
> scroll or the compositor will not be able to manage system gesture
> recognition or transform the behaviour of the trackpad to, for example
> ignore touches with the thumb (while is resting on the bottom of the
> clickpad) and use it to click while drag is enabled with the index
> finger.
scroll events in libinput/wayland have a value, they're not just button
presses like in X. if you want to implement smooth scrolling on the
client side that can be done already.
ignoring touches with the thumb while ... - that's pretty much what
we're doing already in libinput.
system gestures: the whole point of libinput is to provide an input
stack for wayland compositors so we don't have to implement this
multiple times. If we need system gestures in the compositor, we'll
implement them in libinput.
Cheers,
Peter
> Plus it'll not be possible to port apps like Touchegg or
> BetterTouchTool (OS X).
>
> Please don't misunderstand me, you guys are doing an *excellent* work
> with Wayland and libinput, I only would like to point that implementing
> this stuff in the clients, frameworks (Qt/GTK) and/or compositors could
> add some amazing features missing at the moment in the Linux desktop but
> present in compositors like SurfaceFlinger or the OS X compositor.
>
> Maybe a flag to receive the touchpad input raw or processed could be a
> good solution to everyone.
>
> > it's fairly new and the documentation hasn't been updated yet. configure
> > weston with --enable-libinput-backend and that should get you started.
>
> Thank you very much, I'm going to recompile this afternoon Weston to
> have a look to the libinput implementation
>
>
> 2014-06-03 0:25 GMT+01:00 Peter Hutterer <peter.hutterer at who-t.net
> <mailto:peter.hutterer at who-t.net>>:
>
> On Mon, Jun 02, 2014 at 12:45:51PM +0100, José Expósito wrote:
> > Hi Peter,
> >
> > I have checked the libinput implementation and, correct me if I'm
> wrong, I
> > have seen that 2 fingers click is interpreted as right click, 3
> fingers
> > click is interpreted as middle click and there are some special
> rules for
> > specified trackpads, like corner clicks.
>
> there are some special rules for clickpads, specifically a click with a
> finger resting on one of the software-button areas will produce a right
> or middle click.
>
> > Does that mean that the other MT events are not sent to the
> clients? Could
> > it be possible to get the 2 fingers pinch gesture from a QML
> client for
> > example?
>
> not from a touchpad, not at this point. There are some rough plans
> but we've
> pretty much deferred them until we had the basics sorted with libinput.
>
> > So mainly my question is: is it possible to port (
> > https://code.google.com/p/touchegg/) as a wayland compositor, for
> example
> > to manage desktop specified gestures, and still use client
> gestures like
> > pinch and zoom?
>
> eventually yes, but not at this point. as I said in the previous
> email you
> just won't have access to the data. I think a sensible solution here
> is to
> have libinput send semantic events like "pinch", "rotate", etc. and then
> have the compositor hook into those. the actual compositor part would be
> quite small and have no actual gesture recognition, that would be done
> inside libinput. but we're just not there yet.
>
> > By the way, I compiled Wayland/Weston as specified here:
> > http://wayland.freedesktop.org/building.html
> >
> > And QtWayland as specified here:
> > http://wayland.freedesktop.org/qt5.html
> >
> > But I don't see any references to the forked libinput library.
> Does that
> > mean that I should compile libinput and recompile Wayland/Weston
> against
> > this library instead of the system one?
> >
> > I'm sorry for all the questions, but I didn't find any
> documentation about
> > that.
>
> it's fairly new and the documentation hasn't been updated yet. configure
> weston with --enable-libinput-backend and that should get you started.
>
> Cheers,
> Peter
>
> > 2014-06-02 4:30 GMT+01:00 Peter Hutterer
> <peter.hutterer at who-t.net <mailto:peter.hutterer at who-t.net>>:
> >
> > > On Sun, Jun 01, 2014 at 11:38:02PM +0100, José Expósito wrote:
> > > > Hi Daniel,
> > > >
> > > > I'm asking because I'm the author of this tool:
> > > > https://code.google.com/p/touchegg/
> > > >
> > > > That is exactly what you mention but for X11. So I'd like to
> port it to
> > > > Wayland if it is possible of course.
> > > >
> > > > > The intention was to reserve trackpad
> > > > > gestures for a gesture interpreter
> > > > > which lives in the compositor and is
> > > > > properly integrated with, e.g., scrolling
> > > > > and tap-to-click.
> > > >
> > > > Does this mean that it is possible to get multi touch
> gestures in the
> > > > compositor at the moment?
> > > > Will or is it possible to use both approach? I mean, get
> system gestures
> > > in
> > > > the compositor and app specified gestures in the clients,
> like in OS X.
> > >
> > > the input stack in weston atm is that you get touch events from a
> > > direct-touch MT device raw and unprocessed (save for mapping),
> but for
> > > touchpads some input events are interpreted by the stack
> (libinput or
> > > evdev-touchpad.c) and then passed on as pointer events, you
> don't see the
> > > MT
> > > bits of those.
> > >
> > > Cheers,
> > > Peter
> > >
> > >
> > > > Thank you very much!
> > > > El 01/06/2014 23:24, "Daniel Stone" <daniel at fooishbar.org
> <mailto:daniel at fooishbar.org>> escribió:
> > > >
> > > > > Hi,
> > > > >
> > > > >
> > > > > On 1 June 2014 02:03, José Expósito
> <jose.exposito89 at gmail.com <mailto:jose.exposito89 at gmail.com>> wrote:
> > > > >
> > > > >> And I say more or less because it is necessary to put 3
> fingers on the
> > > > >> trackpad to start moving the rectangles...
> > > > >> Anyway, the program is not working on Weston. My question
> is, is that
> > > > >> because Weston doesn't implement multitouch support or
> because Wayland
> > > > >> doesn't support it at the moment? Could it be possible to
> implement
> > > > >> multitouch support in a custom compositor?
> > > > >>
> > > > >
> > > > > Wayland doesn't (currently) support touchpad gestures for
> arbitrary
> > > > > clients; trying to do it for X11 uncovered a whole host of
> really
> > > subtle
> > > > > and annoying issues. The intention was to reserve trackpad
> gestures
> > > for a
> > > > > gesture interpreter which lives in the compositor and is
> properly
> > > > > integrated with, e.g., scrolling and tap-to-click.
> > > > >
> > > > > Can I ask if you had a specific usecase in mind?
> > > > >
> > > > > Cheers,
> > > > > Daniel
> > > > >
> > >
> > > > _______________________________________________
> > > > wayland-devel mailing list
> > > > wayland-devel at lists.freedesktop.org
> <mailto:wayland-devel at lists.freedesktop.org>
> > > > http://lists.freedesktop.org/mailman/listinfo/wayland-devel
> > >
> > >
>
>
More information about the wayland-devel
mailing list