Too easy to accidentally click when chording to scroll

[GoogleCodeExporter]

The double-finger chording that is used to scroll can sometimes cause 
accidental remote mouse 
down or up events. To fix this, it will probably have to have a small time 
delay during which mouse 
events are not sent.

For instance, the delay between the first and second finger touching to scroll 
may be 0.2 seconds 
(random guess). With no delay, a mouse down will be sent and then scrolling 
mode is entered. No 
mouse up will follow when the fingers are released. If there was a small delay 
before sending the 
mouse down, this wouldn't happen.

It will be necessary to gather some real statistics about the delta between the 
first and second 
finger hitting the screen before the delay can be decided upon.

Original issue reported on code.google.com by crf...@gmail.com on 29 Sep 2007 at 2:54

[GoogleCodeExporter]

Original comment by crf...@gmail.com on 29 Sep 2007 at 8:53

• Added labels: Milestone-Release0.4, Priority-Critical
• Removed labels: Milestone-Release1.0, Priority-Medium

[GoogleCodeExporter]

Original comment by crf...@gmail.com on 29 Sep 2007 at 10:15

• Changed state: Started

[GoogleCodeExporter]

Fixed in svn revision 13.

VNCView now has a 0.15 second window before sending a single finger mouse down. 
If a chording mouse down 
happens during that window the original event will never be sent and scrolling 
is started. Otherwise if the time 
elapses, or if a mouse up or dragged event occurs, the mouse down will be sent 
as normal.

The delay could probably be made even smaller, as I was seeing deltas between 
the first and second finger of 
0.008 to 0.020 of a second!

Original comment by crf...@gmail.com on 29 Sep 2007 at 11:23

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by crf...@gmail.com on 15 Oct 2007 at 6:29

• Changed state: Verified