In theory the mouseDown handler should check if the mouse was in the dropdown. The owns() or contains() method is normally used to check that.
On 12/17/13 2:42 AM, "MichaPooh" <[email protected]> wrote: >Hi > >A DropDownList in a Callout(Button) calloutContent closes the Callout >after >selecting an item in the DropDownList... >(using SDK4.11 in a web application - testing with FlashDebugPlayer 11.9) > >This happens because the DropDownManager adds mouseDown triggers to the >systemManager which than closes the callout as well when the DropdownList >closes > >The only workaround I found to prevent this is to get a reference to the >systemManager in my view which uses the Callout and override the >MouseEvent.MOUSE_DOWN and SandboxMouseEvent.MOUSE_DOWN_SOMEWHERE and >stopImmediatePropagation() there.. > >this works, i can select an item without the Callout gets closed but the >downside is that the Callout stays open when i click somewhere outside the >calloutContent what normally would close it. >Re-clicking the calloutButton closes the Callout though.. > >But anyways, i find this solution not optimal because override the >systemMangers mouseDown and stopImmediatePropagation() there could have >other influences on other components in the view and i would have to check >with a flag if the Callout is actually open etc... > >So my question is if anyone sees another workaround for this problem or if >this could be considered as a bug? > > > >-- >View this message in context: >http://apache-flex-users.2333346.n4.nabble.com/DropDownList-in-a-Callout-B >utton-closes-the-Callout-after-selecting-an-item-in-the-DropDownList-tp420 >4.html >Sent from the Apache Flex Users mailing list archive at Nabble.com.
