1. 23 Sep, 2014 2 commits
  2. 24 Aug, 2014 1 commit
  3. 21 Jul, 2014 2 commits
  4. 15 Jul, 2014 2 commits
  5. 02 Jul, 2014 2 commits
  6. 25 Jun, 2014 2 commits
  7. 23 Jun, 2014 6 commits
  8. 19 Jun, 2014 2 commits
  9. 16 Jun, 2014 1 commit
  10. 09 Jun, 2014 3 commits
  11. 03 Jun, 2014 2 commits
  12. 30 May, 2014 1 commit
  13. 27 May, 2014 1 commit
  14. 23 Apr, 2014 1 commit
  15. 22 Apr, 2014 1 commit
    • Jonas Ådahl's avatar
      Introduce seat wide button and key count API · 604f22eb
      Jonas Ådahl authored
      Compositors will need to keep provide virtual devices of supported
      generic device types (pointer, keyboard, touch etc). Events from each
      device capable of a certain device type abstraction should be combined
      as if it was only one device.
      For key and button events this means counting presses of every key or
      button. With this patch, libinput provides two new API for doing just
      this; libinput_event_pointer_get_seat_button_count() and
      With these functions, a compositor can sort out what key or button events
      that should be ignored for a virtual device. This could for example
      look like:
      event = libinput_get_event(libinput);
      switch (libinput_event_get_type(event)) {
      	device = libinput_event_get_device(event);
      	seat = libinput_event_get_seat(device);
      	pevent = libinput_event_get_pointer_event(event);
      	if (libinput_event_pointer_get_button_state(pevent) &&
      	    libinput_event_pointer_get_seat_button_count(pevent) == 1)
      	else if (libinput_event_pointer_get_button_state(pevent) &&
      		 libinput_event_pointer_get_seat_button_count(pevent) == 0)
      Signed-off-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
      Reviewed-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  16. 10 Apr, 2014 1 commit
  17. 06 Mar, 2014 1 commit
  18. 26 Feb, 2014 2 commits
    • Jonas Ådahl's avatar
      Split up the touch event into the different touch types · 6f0ca1a3
      Jonas Ådahl authored
      Instead of having one touch events representing different types of touch
      events by providing a touch type, have one separate event type per touch
      type. This means the LIBINPUT_EVENT_TYPE_TOUCH is replaced with
      Signed-off-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
    • Jonas Ådahl's avatar
      Add seat wide slot to touch events · e80cff7b
      Jonas Ådahl authored
      Since a Wayland compositor have to represent all touch devices of a seat
      as one virtual device, lets make that easier by also providing seat wide
      slots with touch events.
      Seat wide slots may be accessed using
      Signed-off-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
  19. 19 Feb, 2014 1 commit
  20. 10 Feb, 2014 2 commits
  21. 03 Feb, 2014 1 commit
    • Jonas Ådahl's avatar
      Replace output screen size callback with transform helpers · 1f130404
      Jonas Ådahl authored
      Instead of automatically transforming absolute coordinates of touch and
      pointer events to screen coordinates, the user now uses the corresponding
      transform helper function. This means the coordinates returned by
      libinput_event_pointer_get_absolute_y(), libinput_touch_get_x() and
      libinput_touch_get_y() has changed from being in output screen coordinate
      space to being in device specific coordinate space.
      For example, where one before would call libinput_event_touch_get_x(event),
      one now calls libinput_event_touch_get_x_transformed(event, output_width).
      Signed-off-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>
  22. 31 Jan, 2014 1 commit
    • Peter Hutterer's avatar
      tools: add a tool for basic event debugging · 3444b29c
      Peter Hutterer authored
      Simply prints the various events to make it easier to check what's coming out
      of libinput. Works for --udev (the default) or for --device /dev/input/event0.
      Example output:
      event7 	DEVICE_ADDED	seat0	default
      event8 	DEVICE_ADDED	seat0	default
      event4 	POINTER_BUTTON	 +1.35s	272 pressed
      event5 	POINTER_MOTION	 +2.31s	 -3.00/  2.00
      Time is displayed relative to the starting time.
      Note: statically linked for easier debugging, but we don't distribute it
      (yet) anyway.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: Jonas Ådahl's avatarJonas Ådahl <jadahl@gmail.com>