Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of apostolache.andrei@gmail.com
 designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CBB6E8FE.3F5D7%aharui@adobe.com>
References: 
 <CAO0WCdsfUQ0uWUUE=WtLRbo9VvggFo=bhbwwH9_rR2pLLeTLYA@mail.gmail.com>
	<CBB6E8FE.3F5D7%aharui@adobe.com>
Date: Sat, 21 Apr 2012 18:54:41 +0100
Message-ID: 
 <CAO0WCds7LGO_MzU3ZxhMRrsBNeYWGKa6r7WE0J052qb5QHKGvQ@mail.gmail.com>
Subject: Re: [Proposal] Different behaviour on click and doubleClick on
 UIComponent
From: andrei apostolache <apostolache.andrei@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec54eed0a7812a404be34193d

--bcaec54eed0a7812a404be34193d
Content-Type: text/plain; charset=UTF-8

Doug, Alex I'm pretty sure there should be something in the UIComponent to
make the difference between click & doubleClick event. I didn't investigate
too much in this, it was just something that I had to deal on Friday and
wanted to see if someone else had this problem (mine was a bit more complex
that on click event the component was reposition so the double click was
impossible to be made, but also the component need different behaviour on
click & double click).
What I don't know for sure is why there is the
*doubleClickEnabled*property in UIComponent. Maybe a quicker and
simpler solution might be a
callLater on dispatching the "click" event and a flag on "doubleClick"
handler, if the flag is set on true on doubleClick once the callLater is
called is just ignoring to dispatch the click event. Otherwise your
dispatching the click event.
Of course is a simple workaround to be done and maybe a feature that is not
used by a lot of people, but won't mess with the functionality of
UIComponent, it will be available only if you set doubleClickEnabled, but I
think that UIComponent should be the class to have this because I already
had the same request on a Group, Button and on a ItemRenderer.

Regards,
Andrei.

On Fri, Apr 20, 2012 at 6:20 PM, Alex Harui <aharui@adobe.com> wrote:

>
>
>
> On 4/20/12 8: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 the
> > expectation would be: click received (should obfuscate it for 300 ms to
> see
> > if the user is going for a double click), if second click happens trigger
> > doSomethingElse(), otherwise trigger doSomething().
> >
> These requests are why we need to find an efficient plug-in model for the
> SDK.  Then you can alter this behavior and not mess up someone who does
> need
> the click when it happens.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>

--bcaec54eed0a7812a404be34193d--