Should be doable. Please file a bug in JIRA. You're welcome to submit the recommended changes as a patch as well.
On 11/18/13 6:59 AM, "MVBaker" <[email protected]> wrote: >I'm using PaperVision3d and a click on an interactive object is causing a >crash. I went through their code and found that they're instantiating a >MouseEvent extended class called VirtualMouseMouseEvent. Later in their >code >they're testing to see if an event they're processing is an event of this >type and issuing a return to prevent an infinite loop. However, during the >process the event reaches Flex frameworks SystemManager/mouseEventHandler >and their VirtualMouseMouseEvent is replace with a new MouseEvent so their >test fails and the infinite loop is created causing the app to crash. >Can the SystemManager first check to make sure it's dealing with a >MouseEvent and not an extended class before replacing it or could it >replace >it with the same class? > >TIA, >Mike > > > > >-- >View this message in context: >http://apache-flex-users.2333346.n4.nabble.com/Possible-bug-in-MouseEvent- >handling-tp3804.html >Sent from the Apache Flex Users mailing list archive at Nabble.com.
