My idea was that using the getDefinitionByName would allow the function to work as intended with whatever extension of MouseEvent was used rather than bypassing it if it was an extended class. Should we only apply this transformation of !cancellable to cancellable if it's the super class? I don't know enough about the inner workings here. While we're looking at this I have a question that I didn't think of yesterday. What happens with the properties of the extended class or if the MouseEvent class gets a new property in a future version? It will get stripped off during this function. Could some kind of deep copy of the object be applied and then just change the one setting that we want to change?
Mike -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Possible-bug-in-MouseEvent-handling-tp3804p3836.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
