1. 05 Mar, 2009 1 commit
  2. 04 Mar, 2009 10 commits
  3. 02 Mar, 2009 1 commit
  4. 28 Feb, 2009 1 commit
  5. 27 Feb, 2009 3 commits
  6. 26 Feb, 2009 5 commits
  7. 25 Feb, 2009 1 commit
  8. 20 Feb, 2009 2 commits
  9. 17 Feb, 2009 1 commit
  10. 06 Feb, 2009 2 commits
  11. 26 Jan, 2009 1 commit
  12. 12 Jan, 2009 1 commit
  13. 10 Jan, 2009 1 commit
  14. 20 Dec, 2008 1 commit
  15. 12 Dec, 2008 2 commits
  16. 04 Dec, 2008 2 commits
  17. 03 Dec, 2008 3 commits
  18. 24 Nov, 2008 2 commits
    • Batchty's avatar
      13c93be3
    • Batchty's avatar
      Ignore moves during tap processing if no finger is down. · 6cbdb0a1
      Batchty authored
      
      
      The Dell Inspiron 1520 with a Synaptics touchpad loves to send event like
      these after every finger release :
      
          time     x    y   z f  w  l r u d m     multi  gl gm gr gdx gdy
         1.563  3224 1625  57 1  5  0 0 0 0 0  00000000   0  0  0   0   0
         1.574  3251 1632  30 1  5  0 0 0 0 0  00000000   0  0  0   0   0
         1.584  3292 1673  10 1  5  0 0 0 0 0  00000000   0  0  0   0   0
         1.594     1 5855   3 2  5  0 0 0 0 0  00000000   0  0  0   0   0
         1.634     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
         1.746     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
         1.897     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
      
      Most of the time these events are ignored by the driver, but sometimes it
      confuses two-finger scrolling and tap detection.
      
      For example, in this log, the first tap is recognized, the second isn't :
      
          time     x    y   z f  w  l r u d m     multi  gl gm gr gdx gdy
        11.597     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        11.678     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
        11.688     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        11.709  3862 2406   8 1  5  0 0 0 0 0  00000000   0  0  0   0   0
        11.719  3851 2464  67 1  5  0 0 0 0 0  00000000   0  0  0   0   0
        11.729  3849 2407  35 1  4  0 0 0 0 0  00000000   0  0  0   0   0
        11.739  3858 2578   5 1  9  0 0 0 0 0  00000000   0  0  0   0   0
        11.749  3858 2578   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
        11.850     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        11.860     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
        12.073     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        12.083     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
        12.347     1 5855   4 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        12.357  3844 2381  56 1  4  0 0 0 0 0  00000000   0  0  0   0   0
        12.377  3848 2361  32 1  4  0 0 0 0 0  00000000   0  0  0   0   0
        12.388     1 5855   3 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        12.398     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        12.408     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
        12.428     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
      
      The problem with the second tap is that the driver check if the movement from
      (3848,2361) to (1,5855) is over TapMaxMove before it checks for a finger release.
      So the driver considers it as a (short) finger move.
      Add the condition ''the finger is still present'' to the 'move' condition, so
      we ignore these moves..
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@redhat.com>
      Signed-off-by: default avatarSimon Thum <eGore@gmx.de>
      Signed-off-by: Henrik Rydberg's avatarHenrik Rydberg <rydberg@euromail.se>
      6cbdb0a1