Comments on: Quick Tip: stage.mouseX on Android http://blog.yoz.sk/2010/10/quick-tip-stage-mousex-on-androi/?utm_source=rss&utm_medium=rss&utm_campaign=quick-tip-stage-mousex-on-androi My life, my work Tue, 23 Apr 2013 09:47:04 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Jozef Chúťka http://blog.yoz.sk/2010/10/quick-tip-stage-mousex-on-androi/comment-page-1/#comment-4430 Jozef Chúťka Mon, 31 Jan 2011 10:18:48 +0000 http://blog.yoz.sk/?p=2541#comment-4430 Hi Tamas,
now it sounds like device specific issue, thank you for a feedback. You have made a nice solution indeed. I think I would recommend to transform local mouseX, mouseY values to global ones, and test against flash stageWidth, stageHeight and 0, 0 also.
… + maybe considering some offset to these values because when you use the same flash on a desktop you can drag mouse outside the flash box and the valid values goes to negative or higher than stage size.

]]> By: Tamas Gronas http://blog.yoz.sk/2010/10/quick-tip-stage-mousex-on-androi/comment-page-1/#comment-4412 Tamas Gronas Fri, 28 Jan 2011 13:12:53 +0000 http://blog.yoz.sk/?p=2541#comment-4412 Hi,

I have now the same issue in my current project, but the number what I get is different from yours. My mouseY is 89481878.8. Is it maybe depends on devices?
Anyway I solved this problem in the following way:
if the mouseX or mouseY is greater than the width or height of the current display object when I check mouse coordinates on, set the correct values.

I hope it will be useful.

Cheers!

Tamas

]]>