Norman Vine writes: > Note this just requires positioning the cursor from the center > by the % of 'stick' in % of screen space on entry into Yoke_Mode > > I believe this is real close to the 'essence' of a resolution independent > 'relative' coordinate system > > All that is needed is a way of storing 'mouse state' per mode
When you switch into a mode, you would need to initialize to the current property value, not to the previous screen position -- the property value very likely has changed since the last time you were in the mode controlling it. I never realized that you were doing this in the old mouse code so I didn't pay attention when I still had it configured in, but it seems more difficult than you're suggesting. For example, let's say that in one mode left/right mouse motion is controlling the ailerons when no mouse buttons are pressed, the rudder when the left button is pressed, and the brakes when the right button is pressed -- we're going to have to keep track of each one and warp it to the correct position on any button presses. All the best, David -- David Megginson [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
