Thanks everyone for the advice and this (very) brief introduction to Wayland. It leads me to download the full documentation to learn more.
Le ven. 28 oct. 2016 à 05:40, Carsten Haitzler <[email protected]> a écrit : > On Fri, 28 Oct 2016 13:32:06 +1000 Peter Hutterer < > [email protected]> > said: > > > On Fri, Oct 28, 2016 at 08:25:51AM +0900, Carsten Haitzler wrote: > > > On Thu, 27 Oct 2016 11:51:00 +0200 Carlos Garnacho <[email protected]> > said: > > > > > > > Hey Carsten!, > > > > > > > > On Thu, Oct 27, 2016 at 4:11 AM, Carsten Haitzler < > [email protected]> > > > > wrote: > > > > > On Wed, 26 Oct 2016 06:57:53 +0000 "Alexis BRENON @Wayland" > > > > > <brenon.alexis [email protected]> said: > > > > > > > > > >> Just to be sure that I understand clearly, what you call > 'Toolkit' is > > > > >> libraries like GTK, Qt, and co. that are used by developers to > build > > > > >> their apps, isn't it ? > > > > > > > > > > yes. toolkit == EFL, Qt, GTK+ and others (SDL is kind of a > toolkit), > > > > > FLTK, ... chromium/blink is basically a toolkit of its own etc. > > > > > > > > > > at least looking at gtk3 here it doesn't do momentum with > wheel/axis > > > > > scrolling (out of the box). maybe it needs enabling? > > > > > > > > FWIW, that should happen out of the box whenever we got > > > > wl_pointer.axis_stop on both axes: > > > > https://git.gnome.org/browse/gtk+/tree/gtk/gtkscrolledwindow.c#n3399 > > > > > > > > The usual caveats apply, that doesn't help if the app plays smart and > > > > tries to implement its own scroller widget. > > > > > > i was testing under x with my wheel and things looked pretty boring > > > steppy-steppy. so i was just assuming it needed switching on. :( maybe > i > > > need a full wl compositor-to-kms+libinput for it to work? > > > > you won't get stop events for wheel events, so any kinetic magic would be > > dependent on you guessing when the next wheel event comes in (or > doesn't). > > stop events are only sent for "finger" sources, i.e. on the touchpad. > > oh the way we're doing it is far simpler... we don't need stop events at > all. > just some "move 1 tick up.down" is enough. (or 2 ticks, 3 ticks...) also i > was > using my mouse wheel not a touch pad... so thats probably why. > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) [email protected] > >
_______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
