flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Duane Nickull <du...@uberity.com>
Subject Re: [Proposal] Different behaviour on click and doubleClick on UIComponent
Date Fri, 20 Apr 2012 17:43:03 GMT

On 12-04-20 8:48 AM, "Doug Arthur" <dougarthur@gmail.com> wrote:

>On Fri, Apr 20, 2012 at 9:43 AM, andrei apostolache
><apostolache.andrei@gmail.com> wrote:
>> Hi Scott,
>> Is not about a new component, it's about all spark components that are
>> based on UIComponent. Think for example a simple spark button, <s:Button
>> click="doSomething()" doubleClick="doSomethingElse()"
>> doubleClickEnabled="true" /> if you will try to double click the button
>> first it will trigger doSomething() and then doSomethingElse(), while
>> expectation would be: click received (should obfuscate it for 300 ms to
>> if the user is going for a double click), if second click happens
>> doSomethingElse(), otherwise trigger doSomething().
>The problem you have with a timer, is the speed at wich individuals
>set their double click at the OS level. I've had to use that same
>trick before as well, but if someone has a slower (i.e 500ms) double
>click rate, then you run into the same problem of doSomething()
>getting called before doSomethingElse() gets called. I'd hate to bake
>that into the SDK, since there's no "standard" speed at which double
>click is performed. Of course, unless we surface the ability to change
>that rate, which is a valid option. Unless someone else has a better
>- Doug
I worked with this a bit.  The maximum TO is usually 500 MS.  Note that
the click event itself is fired when the mouse user releases the button,
not on the down click itself.

Is there a public API in the runtime to grab the double-click delay time
from the users system?


COO and Director 
Uberity Technology Corporation
"LiveCycle ES and Mobile Specialists"
@uberity @duanechaos


View raw message