Thanks for the response.

 

Agreed, but when your architecture depends on it I think it is a fairly significant thing to leave out. Or temporarily disable. Granted it is a beta ;)

 

If I could discover a logical way to handle a tree click in conjunction with dragging then I would not have a problem. However I think on a tree that drives the actions of the user interface, double click is better then change, or click. The physical action of a double click is rarely accidental, but I do agree on your points.

 

Oh well, I’ll deal with it. I should be able to fake it with a time variable and click event if there is 500 ms between click events then dispatch…

 

Jason
-----Message d'origine-----
De : [email protected] [mailto:[EMAIL PROTECTED]De la part de Darron J. Schall
Envoyé : mardi 21 mars 2006 15:50
À : [email protected]
Objet : Re: [flexcoders] FB2 :: doubleClick bug event doen't happen

Jason Hawryluk wrote:
i have the same problem, i noticed a doubleClickEnabled property and setting that did not do it for the tree which is the only component i use it on. Seems double click is gone.../ not working.


I'm pretty sure this is a known issue - doubleClickEnabled needs to propagate down to all children in the Flex components, and it currently doesn't do this.  I'm guessing it'll be fixed in the next build.

It's not gone, but the reason doubleClickEnabled was added is because of situations where you really want click events, even if the user clicks fast.  For instance, you wouldn't double-click the down arrow button of a scrollbar, but rather you just want it to fire click events rapidly.

-d


--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to