It shouldn't require javascript. If you listen for MOUSE_LEAVE and dispatch a fake MOUSE_UP that should suffice. I think the fix may go into Flex 3.4 as well.
In general, you cannot mix module versions. The SWF loading the module and the module must be compiled with the same version of Flex otherwise you risk problems. See the Marshall Plan presentation on my blog. Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of djhatrick Sent: Tuesday, June 23, 2009 7:54 AM To: [email protected] Subject: [flexcoders] Re: Sticky Scroll bars I use Firefox, like most in our office. Is this possible with the the help of a javascript library, similar to the way the mouse scroll wheel library works in javascript? if it's just missing a mouseUp, maybe I can add that event and send it into flex, would that work? By the way, Alex, so I've heard that flex 3 modules will run in Flex4. I am 2 months into a new application on Flex3, but I really want to use Flex4, though I am a little concerned on the learning curve since I've done very little with flex 4.0 sdk. Will Flex4 modules run in flex3, or that does sound like a bad idea.. (seems like?) Thanks, Patrick --- In [email protected]<mailto:flexcoders%40yahoogroups.com>, Alex Harui <aha...@...> wrote: > > I hope to fix it in Flex 4. Should work on IE? Some of the other platforms > don't send mouseUp from off the stage... > > Alex Harui > Flex SDK Developer > Adobe Systems Inc.<http://www.adobe.com/> > Blog: http://blogs.adobe.com/aharui > > From: [email protected]<mailto:flexcoders%40yahoogroups.com> > [mailto:[email protected]<mailto:flexcoders%40yahoogroups.com>] On > Behalf Of djhatrick > Sent: Saturday, June 20, 2009 7:46 AM > To: [email protected]<mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Sticky Scroll bars > > > > > > After a mouse up on my flex app the scroll bar still sticks as I move the > mouse around, until another click. This is a real annoying bug, anybody know > if this is going to be addressed? > > How did this bug get out in the first place from QA? >
