When mouse bounds are in effect, a tester of my game noticed strange behaviour that I also could replicate: when moving the mouse pointer to the bound, the pointer stops (as it should). However, when moving the mouse back it seems that you have to travel a virtual distance back before being able to move the pointer again.
For example:
Bound is set to x 180. I move the pointer to 180 and beyond (to 200, perhaps). The pointer stops at 180, but an invisible virtual pointer seems to move on. When moving the mouse back along the negative x axis it seems I have to move 20 pixels before the visible pointer starts to move.
So it seems that the engine keeps track of the actual mouse position while only updating the visible pointer while it's in bounds. This is a bit annoying as it causes the pointer to "stick" to bound edges.
I'm not sure whether this is a bug or not. As a player I think I would find it annoying if moving the mouse a certain distance in one direction and then in the other didn't end my pointer back up at the same place.
Anyone else got any thoughts on this?
But this doesn't happen when in windows or other games ??
Quote from: Pumaman on Wed 06/07/2005 16:22:56
I'm not sure whether this is a bug or not. As a player I think I would find it annoying if moving the mouse a certain distance in one direction and then in the other didn't end my pointer back up at the same place.
Anyone else got any thoughts on this?
If you move the mouse pointer to the edge of the screen and away again it moves immediately.
I think moving the mouse and not having the pointer respond is, if not a bug, at least unusual.
Anyway, if you have any kind of mouse acceleration switched on you will find that moving one way then the other won't necessarily end the pointer up in the same place (try a fast right then a slow left).
Well, I think the mouse pointer should act the same way it does when moving to the edge of the screen.
Sorry to bump an old thread, but I ran into this and now have something to say as well (and only do it because this issue hadn't been resolved).
Basically, I think Simulacra and Steve have the right idea - this is odd behaviour, and can cause for brief but unpleasant situations of the mouse failing to respond as expected. Setting bounds basically limits the mouse's movement, yes? Then I would expect, as a player, that the edges I can see are actual edges, and that the mouse won't go past them.
Ok, I'm sold. I'll look into it.