|
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, Ill 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
|
- RE: [flexcoders] FB2 :: doubleClick bug event doen't happen Jason Hawryluk
- RE: [flexcoders] FB2 :: doubleClick bug event doen't h... Jason Hawryluk
- RE: [flexcoders] FB2 :: doubleClick bug event doen't h... Joan Tan
- [flexcoders] FB2 :: Flex printing Dima Ulich
- Re: [flexcoders] FB2 :: Flex printing Phil Marston
- RE: [flexcoders] FB2 :: Flex printing David Mendels
- RE: [flexcoders] FB2 :: Flex printing Dima Ulich
- Re: [flexcoders] FB2 :: Flex prin... Carlos Rovira
- RE: [flexcoders] FB2 :: Flex ... David Mendels
- Re: [flexcoders] FB2 :: Flex ... Carlos Rovira
- RE: [flexcoders] FB2 :: Flex ... Mika Kiljunen

