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().
I hope it makes more sense. Thanks, Andrei. On Fri, Apr 20, 2012 at 3:29 PM, Guthmann, Scott <[email protected] > wrote: > > in some cases you might need to have different behavior for a > button/custom component based on UIComponent for click and double click. > > An workaround will be to start a 300-400 millisecond timer in your click > handler to delay your actions (in case the user will go for a > double-click), but I think the elegant way will be that the UIComponent > should take care of this once you set on true > > doubleClickEnabled. > > Andrei - the project could use extra custom [Spark] components. Do you > have a code for this new component you can show us on your white board? > Please post what you have written and then ask this list to review what you > have done and provide feedback. If you have use cases for this component > and the functionality cannot be done with other existing custom components, > then the Apache Flex project would benefit from having this additional > option. > > Thanks for the input! > > Regards, > > Scott Guthmann > Direct | 303.885.9485 > E-mail | [email protected] > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > . . . . . . . . . . . . . . . . . . > This electronic message transmission contains information from the Company > that may be proprietary, confidential and/or privileged. The information is > intended only for the use of the individual(s) or entity named above. If > you are not the intended recipient, be aware that any disclosure, copying > or distribution or use of the contents of this information is prohibited. > If you have received this electronic transmission in error, please notify > the sender immediately by replying to the address listed in the "From:" > field. > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > . . . . . . . . . . . . . . . . . . > > -----Original Message----- > From: andrei apostolache [mailto:[email protected]] > Sent: Friday, April 20, 2012 4:45 AM > To: [email protected] > Subject: [Proposal] Different behaviour on click and doubleClick on > UIComponent > > Hi. > > It might be a weird proposal, but in some cases you might need to have > different behavior for a button/custom component based on UIComponent for > click and double click. > An workaround will be to start a 300-400 millisecond timer in your click > handler to delay your actions (in case the user will go for a > double-click), but I think the elegant way will be that the UIComponent > should take care of this once you set on true doubleClickEnabled. > > Regards, > Andrei. > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.1913 / Virus Database: 2411/4947 - Release Date: 04/19/12 >
