Carbon double-clicking undetectable under load

[GoogleCodeExporter]

See attached program.  Clicks are delayed for too long, so they miss the 
timeout to become double 
(or triple) clicks.  Commenting out fps_limit (which is simulating a program 
doing lots of rendering) 
avoids the problem.

Original issue reported on code.google.com by Alex.Hol...@gmail.com on 25 Jul 2007 at 12:22

Attachments:

• click.py

[GoogleCodeExporter]

Addressed in r1064.  All queued events are dispatched at once now, which will 
alleviate the problem most of 
the time.

In theory an unlucky user might click twice on either side of the 
dispatch_events iteration, causing it not to be 
registered as a double-click.  This becomes more likely as iterations become 
less frequent (as frame-rate 
drops).  A good idea for apps encountering such a problem would be to 
distribute rendering over multiple 
iterations (or, equivalently, to intermix multiple dispatch_events within the 
one rendering loop).

A quick look at Windows/Linux code suggests that this is already the behaviour 
on those platforms, but this is 
untested.

Original comment by Alex.Hol...@gmail.com on 25 Jul 2007 at 12:29

• Changed state: Fixed