Comment 5 for bug 1215463

Revision history for this message
Sebastien Bacher (seb128) wrote :

Sorry for not commenting on that earlier...

Just as a comment, I don't know how you are doing your user testing but from what we see in Ubuntu/on launchpad, the current settings are working quite nicely. We tried quite some different behaviour, timing, options in the past and we always had some slashback/unhappy users. We didn't really get any complain from the current configuration though. Is the feedback one you got from your users/customers or is that just the feeling from the system76 team looking at the polish of the OS?

> The problem is that on Ubuntu, this creates an annoying amount of cursor wiggle. Competing platforms don't have this problem,
> so this needs to be improved on Ubuntu.

what are competing platforms doing? blocking the cursor move?

> block accidental tap-to-click (which seems unlikely something you can do by mistake with your palms).

not sure what makes you think it's "unlikely", before we added that syncdaemon use it was trivial to miss-click by holding your hands over the touchpad area, some touchpads are just weird acting.

see e.g https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/240738 and the duplicates/comment

> Without the "-t" option, syndaemon will block cursor movement,

right, that's wrong, we have been there, see https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/801763

blocking movement feels wrong, you type than move to the touchpad and try to move the cursor and it doesn't react, that's a very confusing/frustrating user experience

> 500ms seems like about the sweet spot

0.5 was creating issues for some users, see https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/962958