1. 18 Aug, 2020 8 commits
  2. 08 Aug, 2020 1 commit
  3. 18 Feb, 2019 1 commit
  4. 27 Oct, 2014 1 commit
  5. 25 Aug, 2014 1 commit
  6. 06 Jan, 2014 2 commits
  7. 17 Dec, 2012 1 commit
  8. 10 Dec, 2012 1 commit
  9. 07 Nov, 2012 3 commits
  10. 02 Nov, 2012 1 commit
  11. 29 Oct, 2012 2 commits
  12. 13 Jun, 2012 1 commit
  13. 02 Mar, 2012 13 commits
  14. 02 Feb, 2012 1 commit
    • Peter Hutterer's avatar
      specs: explain touch behaviour for dependent devices · 217afacd
      Peter Hutterer authored
      Dependent devices don't send touch events until the interaction is a true
      touch interaction (i.e. doesn't just serve to move the pointer). Once that
      happens, all touchpoints send touch events exclusively. Pointer movement
      restarts once we're down to one touch that controls the pointer again.
      
      For clients listening to touch events in addition to pointer events, this
      also means that a two-finger tap looks identical to holding one finger down
      and tapping with a second-finger. Both actions will result in short
      TouchBegin/TouchEnd sequences for both fingers.
      
      The above is the default behaviour we expect from touchpads, the protocol is
      more generically worded to leave more room for drivers to decide when a
      touch only controls the pointer and when it doesn't.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: default avatarChase Douglas <chase.douglas@canonical.com>
      217afacd
  15. 31 Jan, 2012 3 commits