1. 01 Sep, 2010 2 commits
  2. 22 Jul, 2010 3 commits
  3. 21 Jul, 2010 5 commits
    • Chris Bagwell's avatar
      Align EmulateTwoFinger* docs to current behavior. · abb448a2
      Chris Bagwell authored
      
      
      This corrects man page to mention EmulateTwoFingerMinW
      and EmulateTwoFingerMinZ are considered together.  Old
      man page read like driver would emulate two-finger even
      if only pressure OR width (but not both) were supported.
      
      Next, add note to align man page with patch that defaults
      to enabling two-finger emulation on hardware that does not
      support two-finger detection but does support pressure and
      width detection.
      Signed-off-by: default avatarChris Bagwell <chris@cnpbagwell.com>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      abb448a2
    • Chris Bagwell's avatar
      Default to 2-finger emulation when HW supports it · ffa6dc28
      Chris Bagwell authored
      
      
      Ideally, emulating 2-fingers should just work on hardware
      were it can be supported. This patch is to do that.
      
      Currently, emulateTwoFingerMinW defaults to 7. Most kernel
      drivers do not support reporting finger width and so can't get above
      MinW of 7. Synaptics devices hardcode width value to 5 when
      hardware doesn't support width and 7 is a good threshold to detect
      2 fingers on hardware that does. bcm7954 are only other devices
      that report width and they support reporting DOUBLETAP and wouldn't
      need emulation anyways.
      
      emulateTwoFingerMinZ defaulted to a really high value so never
      let Synaptics devices to emulate 2-fingers by default.
      Changed default to a low value (same as FingerHigh) when hardware
      doesn't support DOUBLETAP and supports width so emulations
      will now work by default in all the right cases.
      
      I'm working to get kernel to stop reporting ABS_TOOL_WIDTH unless
      hardware really supports it.  If that would have been behavior
      in first place then we could also default to 2-finger scrolling as
      well.  Since its not reliable, we should continue defaulting to
      side scrolling.
      
      Config GUI's will want to now allow switching between 2-finger and edge
      scrolling when new property indicates width is supported.  GUI's should
      also update the above MinZ and MinW's to values similar to our defaults.
      Signed-off-by: default avatarChris Bagwell <chris@cnpbagwell.com>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      ffa6dc28
    • Chris Bagwell's avatar
      Document Capabilities property additions in man · e2a247a7
      Chris Bagwell authored
      
      
      Documents has_pressure and has_width additions.
      Signed-off-by: default avatarChris Bagwell <chris@cnpbagwell.com>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      e2a247a7
    • Chris Bagwell's avatar
      Expose width support in capabilites properity. · 75459b1c
      Chris Bagwell authored
      
      
      Some properties are only valid with hardware supports
      width.  Namely, *MinW properties.  Config GUI's may
      wish to disable/grey out options related to width support.
      
      This combined with pressure property is good indication when
      2 finger scrolling can be supported using emulation.
      Signed-off-by: default avatarChris Bagwell <chris@cnpbagwell.com>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      75459b1c
    • Chris Bagwell's avatar
      Expose pressure support in capabilities property. · 51e9bb81
      Chris Bagwell authored
      
      
      Some properties are only valid when hardware supports
      pressure.  For example, the *MinZ and *MaxZ options.
      Config GUI's may wish to disable/grey out config
      options related to pressure since not all hardware supports
      it.  This will allow for that.
      
      Also, change setting of priv->has_pressure to boolean
      value so its value will always fit in 8-bit that
      properities report.
      Signed-off-by: default avatarChris Bagwell <chris@cnpbagwell.com>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      51e9bb81
  4. 19 Jul, 2010 1 commit
    • Chris Bagwell's avatar
      Make default checks for x, y, w, and p separate. · cc9d3415
      Chris Bagwell authored
      
      
      Some input devices will not return any ranges and
      current code seems geared towards those.  It assumed
      if invalid X/Y ranges then that was only case for invalid
      W and Pressure.
      
      Synaptics kernel drivers have been returning valid
      X/Y/Z values but invalid 0/0 values for P.
      
      Split up checks to allow setting defaults for any combination
      of unspecified or invalid values.
      
      I also think there was a bug in older code.  It seemed odd
      it was checking minx > maxx but miny < maxy.  I changed both
      to ">=" so that it also catches kernel reports of 0/0 and
      logically invalid ranges (i.e. 6/6 or 9/1).
      Signed-off-by: default avatarChris Bagwell <chris@cnpbagwell.com>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      cc9d3415
  5. 22 Jun, 2010 1 commit
  6. 17 Jun, 2010 7 commits
  7. 16 Jun, 2010 9 commits
  8. 07 Jun, 2010 4 commits
  9. 02 Jun, 2010 2 commits
  10. 31 May, 2010 6 commits