- Jan 15, 2015
-
-
Peter Hutterer authored
Note: soname bump Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
We specify a bunch of other (static) things in the .in file, let's be consistent. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Fixes doxygen build with custom builddirs Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Some devices require more than just flipping around the buttons, such as tablets. When it comes to devices like tablets, because the position of the palm rest is on the right, the entire tablet has to be flipped around in order to be usable by lefties. As such, this requires that we reverse the coordinates of the tablets in addition to flipping the buttons on the tablet. As such, renaming these functions so that they aren't specific to devices where only the buttons are flipped seems appropriate. Signed-off-by: Stephen Chandler Paul <thatslyude@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This is merged on top of the wheel normalization patches. Those introduced an axis source and an extra "discrete" value to the various internal and external APIs. This branch changed from a single value to passing dx/dy into all scroll events. The conflicts are to change everything to take x, y, x_discrete, y_discrete as values (and the source axis mask of course). Conflicts: src/evdev-mt-touchpad-edge-scroll.c src/evdev.c src/libinput-private.h src/libinput.c
-
- Jan 14, 2015
-
-
Peter Hutterer authored
The recent normalization of wheel events means we get the angle in degrees but we don't know how this corresponds to clicks. The M325 has a 20 degree click angle, most other mice have 15 degrees. So an angle of 60 can be 3 or 4 click events. Most clients care more about the click count than the angle on a mouse wheel. Provide that value when needed. Adding a discrete value to the axis event leaves the possibility of defining discrete units for finger/continuous scroll sources in the future. Right now, these will always reuturn 0. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Jan 13, 2015
-
-
Peter Hutterer authored
Sending separate axis events instead of one unified events is limiting, especially when simultaneously scrolling in both directions and the caller tries to implement kinetic scrolling. Take a page from the tablet-support branch and instead implement the axis event as a generic event that can contain multiple axes simultaneously. Right now we only have two (scroll) axes and we could easily just check both for non-zero values. If we want to allow further axes in the future, we need a check whether an axis is set in an event, that's what libinput_event_pointer_has_axis to scroll events() is for. We also need the mask to notify of a scroll stop event, which could otherwise be confused as a vertical-only or horizontal-only event. This is an API and ABI break. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
-
Peter Hutterer authored
Similar to the mouse resolution, let's make the scroll distance a sensible predictable value. Most mice use a 15 degree angle per scroll click, so let's change to that. This will alter behaviour in clients that expect 10. We return doubles for the axis value, so that leaves the option of really fine-grained step sizes in the future. We currently assume all mice have 15 degree angles. Like the DPI settings, it will require a udev property to be set. Patch for that to follow. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
-
Peter Hutterer authored
prop isn't the full property line, just the value. And document the return value too while we're at it. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 11, 2015
-
-
Main has unused parameters argc and argv. Since they are unused and C 99 allows to prototype main as 'int main(void)', remove them and replace by void. It fixes build when unused parameters are treated as errors. Signed-off-by: Marek Chalupa <mchqwerty@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 08, 2015
-
-
Peter Hutterer authored
Under gdb, signalfd will still deliver the signal when gdb itself is interrupted and quit event-debug. For a debugging tool, that's not optimal. Switch to a normal signal handler instead, signalfd is overkill here anyway. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
-
- Jan 07, 2015
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Jonas Ådahl authored
Signed-off-by: Jonas Ådahl <jadahl@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Jonas Ådahl authored
Discreet means to not draw attention. Discrete means non-continuous. Signed-off-by: Jonas Ådahl <jadahl@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 05, 2015
-
-
Peter Hutterer authored
Causes the valgrind tests to fail as tp is considered uninitialized. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
misc.c:562:10: warning: missing field 'expected_dpi' initializer [-Wmissing-field-initializers] { NULL } Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
We can just set the interface component to NULL directly instead. Fixes clang warnings: litest-mouse.c:38:1: warning: missing field 'touch_move' initializer [-Wmissing-field-initializers] litest-trackpoint.c:38:1: warning: missing field 'touch_move' initializer [-Wmissing-field-initializers] Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Unused since 4913fd7a Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 04, 2015
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Change the seat field widths to match the usual seat0/default. This compresses the output a bit, we're printing too much already. Also, one of my mice has >30 chars, it's annoying to look at. Fix this. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Dec 24, 2014
-
-
Peter Hutterer authored
For a caller to implement/provide kinetic scrolling ("inertial scrolling", "fling scrolling"), it needs to know how the scrolling motion was implemented, and what to expect in the future. Add this information to the pointer axis event. The three scroll sources we have are: * wheels: scrolling is in discreet steps, you don't know when it ends, the wheel will just stop sending events * fingers: scrolling is continuous coordinate space, we know when it stops and we can tell the caller * continuous: scrolling is in continuous coordinate space but we may or may not know when it stops. if scroll lock is used, the device may never technically get out of scroll mode even if it doesn't send events at any given moment Use case: trackpoint/trackball scroll emulation on button press The stop event is now codified in the API documentation, so callers can use that for kinetic scrolling. libinput does not implement kinetic scrolling itself. Not covered by this patch: * The wheel event is currently defined as "typical mouse wheel step", this is different to Qt where the step value is 1/8 of a degree. Some better definition here may help. * It is unclear how an absolute device would map into relative motion if the device itself is not controlling absolute motion. * For diagonal scrolling, the vertical/horizontal terminator events would come in separately. The caller would have to deal with that somehow. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Original patch, before the rebase onto today's master: Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Dec 23, 2014
-
-
Peter Hutterer authored
Previously, the pointer could only be passed into the context on creation time and was immutable after that. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
We want to rebuild whenever it changes Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Add a boolean state machine for two-finger scrolling so we know when we're currently scrolling. If we were scrolling and it stops, pick the active touch as pointer touch so we can go back to pointer movement without having to lift the finger off the touchpad. https://bugs.freedesktop.org/show_bug.cgi?id=86807 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
In preparation for a twofinger_state field, to avoid confusion. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
In a few tests we care about that a specific set of events are in the queue but not about the details of the events (usually checked elsewhere). Instead of manual loops, provide a helper function that also checks that there is at least one of those events in the queue. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The tests ignored it when motion events never happened - but that's mostly what these tests are about. This only happened for semi-mt devices that use the bounding box only, not separate touch points. Switching the touch points around that the bounding box doesn't interfere causes the test to work as expected. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The event-gui needs this but it got dropped in 6ee8c585, causing a crash. Oops. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This gives the event gui the ability to use the path backend, and any configuration toggles given on the commandline. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
event-debug and event-gui can and should share this Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-