This AIR app is to be embedded in a consumer electronics product.  It is a 
transparent UI that indirectly controls an underlying map application by 
sending messages via sockets.

The product actually has a joystick and not a mouse and one requirement is that 
moving the joystick will cause the map to pan.  

In development, using a real mouse, when the mouse pointer hits a screen 
boundary, MouseMove events are no longer dispatched in that direction.  In a 
corner, all events cease.  This is causing me problems with continuing to send 
messages to the application to continue panning.

I am hoping the joystick will behave differently, but am also looking for any 
other suggestions.  I have considered using a timer to send repeated increments 
(the back-end app only needs position deltas), but I haven't figured out how to 
stop that.

As far as I can tell, there is no way to set the position of the system cursor. 
 If I could reset the mouse x,y to some positive values when it approached an 
edge, that would work as well.

Is there anyway I can get "deeper" into the mouse event?  If I could get a 
generic "moving" event, that would also suffice.

Any thoughts?

Tracy Spratt

Reply via email to