Re: Optimizing behaviour of Synaptics Clickpad on Sony Vaio Z13

2013-01-06 Thread Peter Hutterer
On Fri, Jan 04, 2013 at 11:41:59PM +0100, Markus Ellinger wrote:
 Am 04.01.2013 07:14, schrieb Peter Hutterer:
  Thanks, that's great. If this patch is added, will we still need to
  manually set a dead area on the buttons? Or is there a possibility
  to change the default config files so that if there are clickpad
  buttons, those are automatically marked as dead area?
 no, I'd rather not make this a default. I'll add an example to the default
 config file but people use their touchpads quite differently and we can't
 tell. specifically, we configure the soft buttons to work as left/right on
 non-apple clickpads but a user who enables tapping is less likely to use the
 buttons. disabling the area for those users is a regression.
 
 So how is the user who uses tapping supposed to do the right mouse
 button click?

usuall two or three-finger tapping. that's the reason why I don't want to
disable this area by default, the buttons take over a significant chunk of
the touchpad that would just stop reacting.

 I think what you're saying really depends on the type of trackpad
 used. For example, my touch pad looks like this one:
 
 http://www.cnet.de/wp-content/uploads/legacy_images/story_media/41557080/sony_vaio_z21_tastatur_touchpad.jpg
 
 The buttons are clearly visible as such and they also contain the
 finger print reader area. I doubt that anyone is temped to use those
 buttons for moving the mouse pointer.

we don't really see this in the driver though, all we see is a surface area
and that the touchpad only has a left-click. to the driver, your touchpad
looks almost identical to mine which merely has to thin lines to mark the
buttons:
http://static.trustedreviews.com/9dcc9f%7C1e55_15341-img9088s.jpg

 Just while I'm at it, is it possible to configure the buttons so
 that merely tapping (not pressing) them issues the right or left
 mouse click? Now that would be sweet.

no, we don't have code for that yet but I'm somewhat hesitant to add it.
given that all clickpads support multiple fingers, using double/triple-tap
gives you the same functionality and it's already integrated into the
various DEs.

Cheers,
   Peter

___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com


Re: Optimizing behaviour of Synaptics Clickpad on Sony Vaio Z13

2013-01-04 Thread Markus Ellinger

Am 04.01.2013 07:14, schrieb Peter Hutterer:

 Thanks, that's great. If this patch is added, will we still need to
 manually set a dead area on the buttons? Or is there a possibility
 to change the default config files so that if there are clickpad
 buttons, those are automatically marked as dead area?
no, I'd rather not make this a default. I'll add an example to the default
config file but people use their touchpads quite differently and we can't
tell. specifically, we configure the soft buttons to work as left/right on
non-apple clickpads but a user who enables tapping is less likely to use the
buttons. disabling the area for those users is a regression.


So how is the user who uses tapping supposed to do the right mouse 
button click?


I think what you're saying really depends on the type of trackpad used. 
For example, my touch pad looks like this one:


http://www.cnet.de/wp-content/uploads/legacy_images/story_media/41557080/sony_vaio_z21_tastatur_touchpad.jpg

The buttons are clearly visible as such and they also contain the finger 
print reader area. I doubt that anyone is temped to use those buttons 
for moving the mouse pointer.


Just while I'm at it, is it possible to configure the buttons so that 
merely tapping (not pressing) them issues the right or left mouse click? 
Now that would be sweet.


Cheers,
Markus

___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com


Re: Optimizing behaviour of Synaptics Clickpad on Sony Vaio Z13

2013-01-02 Thread Peter Hutterer
On Tue, Jan 01, 2013 at 04:33:31PM +0100, Markus Ellinger wrote:
 Hi everyone,
 
 I am using Linux Mint Nadia which ships with X.Org 1.13.0 on a Sony
 Vaio Z13. I experience two problems with the Synaptics driver which
 do not occur on the Windows 7 Professional installation on the same
 machine:
 
 1. Moving the mouse pointer using the touchpad works fine, however,
 everytime when I release the finger from the touchpad, the mouse
 pointer jumps a little bit from its reached position. I guess this
 is because I do not release the finger steady enough and thus
 releasing the finger triggers some additional mouse pointer
 movement. This really is annoying because e.g. when I hover on a
 button, then release the finger to tap the button, often the mouse
 pointer jumps away from the button and the tap clicks the wrong
 button. Is there any way to tell the Synaptics driver in X.org to
 ignore movements when the finger is released? The Synaptics Windows
 driver does not have this problem, here when I release the finger,
 the mouse pointer never jumps. I already tried to play with some
 synclient options but to no avail.

I suspect the cause for this is more the natural shape of your finger. as
you press down, the contact surface increases, and the hotspot you get is
somewhere in the middle. as you release, the contact surface changes and you
get the jump. I can see this here and it's related to how hard you press
before releasing. the harder, the bigger the jump.

there isn't really anything you can tune in the settings for this particular
behaviour. the hysteresis options will help a bit, but hinder some smaller
movement.

really what we need here is some pressure-based smoothening, to prevent
cursor jumps if the pressure changes.
 
 2. The Sony Vaio Z13 has ClickPad buttons. They do react to
 clicks, however, the buttons itself are sensitive to cursor
 movements. I tried to set AreaBottomEdge to exclude the button area
 but when I do this, detection of the right button (as facilitated by
 RightButtonArea... settings in synclient) fails. Is there a way to
 exclude the button area from creating pointer movements and still
 allow the right button to work?

you need
http://patchwork.freedesktop.org/patch/12707/

Cheers,
   Peter

 
 Below I'm giving you my synclient settings. Please let me know if
 you need any more info.
 
 Any help or pointers is greatly appreciated.
 
 Best regards
 Markus
 
 
 Parameters given by Synclient version 1.6.2
 
 Parameter settings:
 LeftEdge= 1772
 RightEdge   = 5468
 TopEdge = 1642
 BottomEdge  = 4524
 FingerLow   = 25
 FingerHigh  = 30
 FingerPress = 256
 MaxTapTime  = 180
 MaxTapMove  = 239
 MaxDoubleTapTime= 180
 SingleTapTimeout= 180
 ClickTime   = 100
 FastTaps= 0
 EmulateMidButtonTime= 0
 EmulateTwoFingerMinZ= 282
 EmulateTwoFingerMinW= 7
 VertScrollDelta = 108
 HorizScrollDelta= 108
 VertEdgeScroll  = 1
 HorizEdgeScroll = 0
 CornerCoasting  = 0
 VertTwoFingerScroll = 0
 HorizTwoFingerScroll= 0
 MinSpeed= 1
 MaxSpeed= 1.75
 AccelFactor = 0.0367175
 TrackstickSpeed = 40
 EdgeMotionMinZ  = 30
 EdgeMotionMaxZ  = 160
 EdgeMotionMinSpeed  = 1
 EdgeMotionMaxSpeed  = 435
 EdgeMotionUseAlways = 0
 TouchpadOff = 2
 LockedDrags = 0
 LockedDragTimeout   = 5000
 RTCornerButton  = 2
 RBCornerButton  = 3
 LTCornerButton  = 0
 LBCornerButton  = 0
 TapButton1  = 1
 TapButton2  = 3
 TapButton3  = 0
 ClickFinger1= 1
 ClickFinger2= 3
 ClickFinger3= 0
 CircularScrolling   = 0
 CircScrollDelta = 0.1
 CircScrollTrigger   = 0
 CircularPad = 0
 PalmDetect  = 0
 PalmMinWidth= 10
 PalmMinZ= 200
 CoastingSpeed   = 20
 CoastingFriction= 50
 PressureMotionMinZ  = 30
 PressureMotionMaxZ  = 160
 PressureMotionMinFactor = 1
 PressureMotionMaxFactor = 1
 ResolutionDetect= 1
 GrabEventDevice = 1
 TapAndDragGesture   = 1
 AreaLeftEdge= 0
 AreaRightEdge   = 0
 AreaTopEdge = 0
 AreaBottomEdge  = 0
 HorizHysteresis = 8
 VertHysteresis  = 8
 ClickPad= 1
 RightButtonAreaLeft = 3620
 RightButtonAreaRight= 0
 RightButtonAreaTop  = 4155
 RightButtonAreaBottom   = 0
 MiddleButtonAreaLeft= 0