I've come across a strange problem when viewing Unity Web players in Safari.
When i open a new window over an active Unity Web player window, the mouse is hidden in that same region for the new window.
The problem goes away when Safari is not in focus.
Anyone else had this problem? - its a bit annoying when you're trying to browse other pages and cant find your mouse
I've just encountered the same issue in the regular Unity player.
It seems that if the unity player is (or is in) the active application and you have Screen.showCursor set to false, Unity will keep the cursor hidden even if the player is no longer the front window.
There are several ways to reproduce this effect:
If you use a custom cursor that tracks the position of the mouse but doesn't show the system cursor, you can open your (non-web) player in windowed mode hit the minimize button, but keep the app active. You'll find that in the screen region where you player was before minimizing the mouse will disappear.
Again, with a custom cursor -- if you open the about box and it opens (or is placed) on top of the unity player, you will not see the system cursor when mousing over the about box...
All this brings me to my question . . . is there a way to determine if the player is in fact the front/top-most window, and if not, be able to then parse that fact and change the cursor setting accordingly?
Developer, Benchtop Creative
Known and logged bug, sorry about that. I'll add some fresh notes to the bug record in the hopes of bumping up the priority a notch or three.Originally Posted by shaunAnyone else had this problem? - its a bit annoying when you're trying to browse other pages and cant find your mouse
I mentioned a web player workaround above but that's obviously not going to work in a stand-alone case. Honestly I'm just not sure if there are any solutions or workarounds in that case, I'll see if I can find any for you (stay tuned).Originally Posted by BasketQaseAll this brings me to my question . . . is there a way to determine if the player is in fact the front/top-most window, and if not, be able to then parse that fact and change the cursor setting accordingly?
Edit: and after inquiring internally there doesn't appear to be a way to do this detection in the stand-alone player. The bug is now on the high-priority list for a 2.x dot-release update.
I've posted more technical details on StackOverflow just in case someone over there may have similar experience as well:
Please help vote it up to help gain more visibility if you feel the issue is legitimate and would also like to see it resolved with an elegant solution. Or if any of you was able to successfully work around or resolve the issue, please do share.
And I also closed my own question on StackOverflow:
Last edited by scchu; 04-08-2011 at 02:31 AM. Reason: Solution to this thread found.