Skip to content
Snippets Groups Projects
  1. Feb 13, 2018
  2. Feb 09, 2018
    • Peter Hutterer's avatar
      tablet: don't set rotation on a tool if we don't have ABS_Z · cbb4ec1e
      Peter Hutterer authored
      Rotation on a tool can either ABS_Z or in the case of the mouse/lens tools a
      combination of ABS_TILT_X/Y. The code assumes that if the rotation on a stylus
      (not mouse/lense) changes, we need to fetch it from ABS_Z. This happens on the
      very first event from the tablet, proximity in invalidates all axes so we can
      send the current state to the caller.
      
      On libwacom-recognized tablets we never set the rotation bit on the stylus, so
      that's all fine. On tablets without libwacom support, the stylus may have a
      rotation bit copied because we have it set thanks to mouse+tilt on the tablet.
      When that first event is handled, we try to access ABS_Z. On tablets without
      ABS_Z like Aipteks, we go boom.
      
      Fix this by checking for ABS_Z during tablet init, if we don't have that axis
      then never set the rotation bit on the tool. That's the only axis where we
      need this, all other axes have a single cause only and thus the tablet bits
      are accurate anyway.
      
      https://bugs.freedesktop.org/show_bug.cgi?id=104939
      
      
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      cbb4ec1e
  3. Feb 07, 2018
  4. Feb 06, 2018
  5. Feb 05, 2018
  6. Feb 01, 2018
  7. Jan 23, 2018
  8. Jan 21, 2018
  9. Jan 18, 2018
  10. Jan 10, 2018
    • Peter Hutterer's avatar
      touchpad: drop the double normalization · 937e6031
      Peter Hutterer authored
      
      Previously, touchpad deltas were converted to 1000-dpi normalized coordinates
      and handled from there. This changed in bdd4264d (1.6)
      when the filter functions started taking device coordinates instead. Since
      then, we used to convert the device delta to normalized coordinates, then
      (often immediately) convert back to device coordinates, albeit for equal x/y
      resolution. This isn't necessary, we can just convert the device coordinates
      to x/y-equal resolution device coordinates and pass those on.
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      937e6031
  11. Jan 09, 2018
  12. Dec 18, 2017
  13. Dec 08, 2017
  14. Nov 30, 2017
  15. Nov 29, 2017
  16. Nov 27, 2017
  17. Nov 21, 2017
  18. Nov 20, 2017
    • Peter Hutterer's avatar
      touchpad: work palm detection into the tap state machine · 46eab975
      Peter Hutterer authored
      Unlike the already-existing thumb detection, a touch may be labelled palm at
      any time, not just during the initial touch down. This requires full
      integration into the tap state machine to unwind properly. For most states, a
      palm detection simply ignores the finger and reverts to the most recent state.
      
      One exception is the case of two fingers down, one finger up followed by the
      remaining finger detected as a palm finger. This triggers a single-finger tap
      but with timestamps that may be from the wrong finger. Since we're within a
      short tap timeout anyway this should not matter too much.
      
      The special state PALM_UP is only handled in one condition (DEAD). Once a
      touch is a palm we basically skip over it from then on. If we end up in the
      DEAD state after a button press we still need to handle the palm up events
      accordingly to be able to return to IDLE. That transition also requires us to
      have an accurate count of the real fingers down (palms don't count) so we need
      a separate nfingers_down counter for tapping.
      
      https://bugs.freedesktop.org/show_bug.cgi?id=103210
      
      
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      46eab975
    • Peter Hutterer's avatar
      test: replace a litest button with a litest key call · f35bb976
      Peter Hutterer authored
      
      Same thing under the hood but still...
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      f35bb976
    • Peter Hutterer's avatar
      test: restore the non-debounced litest_button_click() · 3fea53c3
      Peter Hutterer authored
      
      8cf6893f removed it to make search/replace easier, restore it for the tests
      where we don't want debouncing to automatically be handled.
      
      Still left in place are the various top software button cases. Because of the
      button re-routing through the fallback interface we need those to be
      debounced.
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      3fea53c3
Loading