That has the same downfall of some of the other solutions in that it requires the user to take an action to STOP the panning. This experience is the worse with a joystick.
My current approach, using an OS level functionality to move the mouse position back to center (the pointer is invisible) seems the closest so far. Thanks, Tracy --- In flexcoders@yahoogroups.com, Ian Thomas <i...@...> wrote: > > Tracy, > Can't you take a different approach? This is for panning the map, yes? > > How about, every frame: > > - if the mouseX is less than a certain amount (e.g. is in the left > third of the screen), pan your map left. > - if the mouseX is greater than a certain amount (e.g. the right third > of the screen), pan your map right. > > You could add more complication than that - the further it is to the > edge of the screen, the higher the move acceleration or whatever. > > That should get around your problem - not sure if it'll give you the > user experience you desire, but it could be worth trying. > > HTH, > Ian > > > > On Fri, Jul 31, 2009 at 2:26 PM, Tracy Spratt<tr...@...> wrote: > > > > > > Once the mouse pointer position hits a screen border, further attempts to > > move in that direction do not generate mouseMove events. For example, put > > the pointer in the top left corner, and once you get (0,0), no more events > > are generated. If you put the pointer on a border and wiggle it along that > > border, the changes in the other axis do generate events, but that doesn't > > really help me. > > > > > > > > I do not know what is happening at the AIR runtime/OS/driver level, but the > > mouse and joystick have the same behavior at the application level. > > > > > > > > > > > > Tracy Spratt, > > > > Lariat Services, development services available > > > > ________________________________ > > > > From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On > > Behalf Of Alex Harui > > Sent: Thursday, July 30, 2009 2:58 AM > > To: flexcoders@yahoogroups.com > > Subject: RE: [flexcoders] Re: AIR app, need MouseMove events NOT bounded by > > screen > > > > > > > > > > > > If the app is fullscreen, how can you miss any mousemoves? Does the > > joystick continue to send events the AIR and the mouseMove doesn't get sent > > or is it that the mouseMove doesn't have different coordinates? > > > > > > > > Alex Harui > > > > Flex SDK Developer > > > > Adobe Systems Inc. > > > > Blog: http://blogs.adobe.com/aharui > > > > > > > > From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On > > Behalf Of Tracy Spratt > > Sent: Wednesday, July 29, 2009 9:31 PM > > To: flexcoders@yahoogroups.com > > Subject: RE: [flexcoders] Re: AIR app, need MouseMove events NOT bounded by > > screen > > > > > > > > > > > > Thanks, but my issue is that the AIR app is full screen. And AIR does not > > provide any way to set the system cursor(mouse pointer) position. > > > > > > > > I think I have an interim solution that notes when the mouse position > > reaches a boundary and sends a message to the socket server which calls an > > OS level program to reset the cursor position. As hoped, AIR recognizes > > this action and the next mouse move begins at the reset position. I still > > have some wrinkles to work out but I think this will keep us going until we > > figure out something better. > > > > > > > > Tracy Spratt, > > > > Lariat Services, development services available > > > > ________________________________ > > > > From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On > > Behalf Of Adrian Resa Jones > > Sent: Wednesday, July 29, 2009 1:04 PM > > To: flexcoders@yahoogroups.com > > Subject: [flexcoders] Re: AIR app, need MouseMove events NOT bounded by > > screen > > > > > > > > > > > > Do I understand correctly that you want to track when the mouse > > cursor/joystick leaves the Air App window? I don't see why you shouldn't be > > able to reset the x & y coordinates when they go off of the main application > > window. Not that logic always has anything to do with it. This is another > > one of those things that should be a given. > > > > Maybe this will help: > > > > http://nexus.zteo.com/2008/11/02/flex-how-i-worked-around-mouse_outs-inefficiencies/ > > > > --- In flexcoders@yahoogroups.com, "Tracy Spratt" <tracy@> wrote: > >> > >> 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 > >> > > > > >
