David Megginson writes: > >Norman Vine writes: > > > This was IMHO necessary for the MOUSE_YOKE mode and > > very useful for the other modes. Some of this was compile time > > configurable, FWIW this was fairly tricky to get right at first but > > is fairly straight forward once you figure out what you need. > > > > ie when cycling into YOKE Mode you want the cursor to reflect > > current state of the stick !! > >I don't know how the mouse code ended up, but when I originally wrote >it, this wasn't necessary -- I just used scaled mouse movement to move >the controls, rather than reading an absolute screen position (as I >would with a joystick), so there was no need for the mouse code to >remember the mouse's screen position. I'm doing the same thing now in >the new input.cxx code, and yoke mode seems to work OK.
Yes that works except there is no visual feedback as to where the neutral position is. ie it changes depending on where the mouse cursor is located on entering YOKE_MODE. This is AWKWARD at best By storing the mouse xy between mode changes the cursor when in YOKE_MODE can always be prepositioned so as to have the center of the screen be 'neutral stick'. FWIW The old Mouse code has been that way since about a week after you first submitted it so this is what you have been using :-) Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
