Comment 4 for bug 957623
Revision history for this message
| tbnorth (terry-n-brown) wrote Re: [Bug 957623] Re: Allow user to assign alt-x cmds to mouseclicks | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
On Thu, 22 Mar 2012 13:20:29 -0000
"Edward K. Ream" <email address hidden> wrote:
> Selecting nodes is the heart of Leo's event logic. The code is
> incredibly complex. It's surprisingly easy to break the code, and
> surprisingly hard to get it right. I do not want to mess with that
> code, and for sure I do not want to make the code dependent on race
> conditions.
Fair enough - I don't think the timer approach actually breaks anything
or creates a race condition, but given that all desired use cases are
working without out (i.e. are working with the single-click and
double-click actions firing), there's nothing to gain at this point.
Aside, googling around, it seems the timer approach is used quite a bit
to deal with users double clicking things they're supposed to single
click (which 'general public' users do constantly). If you click
something that pops-up a menu, then click it again, the menu goes away
(Start button in windows for exampled). So a timer's used to ignore
the second click if it comes within the double click interval.