You might be able to work around other controls hijacking your event by using either the CaptureMouse/ReleaseMouseCapture methods, or possibly setting the mouse event (Is)Handled property to false (so that other controls can also catch it). Your particular situation may vary but I've seen buttons catching events and handling them which then means nothing else will handle it. It could also be an internal behaviour in the combobox that is not bubbling the event up so you could customise the combobox (maybe) so that it doesn't. (ie if you really wanted that combobox).
Wish I had a dollar for every weird behaviour thing I found working with UI. It sure keeps your day interesting/challenging. It also means job security from the backend developers that can't wrap their heads around the warped world of UI. hehe. cheers, Stephen On Tue, Jun 8, 2010 at 4:10 PM, Greg Keogh <[email protected]> wrote: > I just thought I’d mention some subtle curious and irritating behaviour I > found yesterday. > > > > You’ve probably all seen Silverlight code that detects mouse enter over a > certain control and animates another control into view. I eventually got one > of these working too, but here’s the trap: If the popup control has a > ComboBox as a child control, opening the combo drop will trigger a mouse > leave from the parent popup and it will decide to close. It seems that the > ComboBox is an aggregate control and something inside it takes the mouse > enter event when you open it. > > > > I couldn’t find a workaround, so I gave up and replaced the ComboBox with a > ListBox and the problem doesn’t happen. > > > > Greg > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > >
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
