It seems this is solved in 10.2.3 version. I changed back to the code I had before 10.2.2 and now it works again.
In version 10.2.2 I "fix" it calling my method in "prePointerUp" instead of "postPointerUp" . Behaviour was worst but it worked.
Hope it helped!