Track as menu will "fix" those buttons that get an onRelease with no initial 
onPress.  However, since onPress and onRelease isn't used, mouseUp and down, 
in Flex 1.5, is controlled by hit testing a movieclip on _root; if you don't 
move the mouse, but the UI does, it doesn't know whats under you until the 
last time you moved.

Have to check in 2.

----- Original Message ----- 
From: "Tracy Spratt" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, October 18, 2005 7:52 PM
Subject: RE: [flexcoders] Flex 1.5 mx.events.LowLevelEvents bug(99911) 
addition


That sounds like this below, from the faq:
***
17. Sometimes, if I don't move the mouse, "click" and "mouseDown" don't
work.
This is a focus issue with the Flash Player, usually when the UI changes
"underneath" the mouse pointer, as in a ViewStack navigation where the
buttons are in the same screen location.

A work around is to add this property to the button tag:

trackAsMenu="true"
***

So I suspect/hope it is fixed in 2.0.
Tracy

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of JesterXL
Sent: Tuesday, October 18, 2005 7:15 PM
To: Flexcoders
Subject: [flexcoders] Flex 1.5 mx.events.LowLevelEvents bug(99911)
addition

Before I log this, wanted to make sure my logic is correct.

- I have a VBox full of dynamically created children (via createChild).
- those children have the ability to change their index by clicking on
up
and down arrow buttons
- clicking the button causes the parent to call setChildIndex to adjust
the
index up or down
- this calls layoutChildren, which in turn re-positions the children...
BUT
does not update the _mouseTracker that is created via
mx.events.LowLevelEvents
- if you click again, the mouseUp event still thinks the same child is
the
target, and thus dispatches this in mouseUp evnets.

Naturally, moving your mouse after clicking fixes it because onMouseMove

gets called twice.

What I did to fix it so you don't have to move your mouse is to
immediately
call
mx.events.LowLevelEvents.onMouseMove twice after setChildIndex.

Works like a charm, but man, that was HARD to find...!

Is it a confirmed bug and should I file?

--JesterXL





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












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









------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/nhFolB/TM
--------------------------------------------------------------------~-> 

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

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcoders/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 




Reply via email to