David Megginson writes: > >Norman Vine writes: > > > I am not so sure that we don't want both an pulsed 'euler' angle > > setter 'keypoard and hat' AND a separate mouse controller. > > > > I mean after all you don't have to go into Mouse View mode and this > > way I can use the keyboard to set the default viewin offsets and I > > the mouse can be used for 'quick look arounds'. > >I don't think this is a good architectural choice -- having two (or >more) different ways of doing the same thing makes life hard for all >the rest of the programmers, as we've seen over the past few weeks >with the viewer code.
Why -- all you need to do is document it Consider this scenario I want my normal view down 20% slightly to the left I can set these with the keys or whatever I can now use the mouse to spin about do what ever in mouse mode when I leave mouse mode I am back at my normal position >If we did decide to support Norm's scenario, I think the right >approach would be to push the current viewer state then pop it out >again. That would be a good, general solution that would work for >anything (mouse, keyboard, joystick, graphic tablet, head-mounted >thingy, or what-have-you). I have been pushing for a 'stack based approach' for all User Input Modes for years good to see I might finally be getting a little support for this :-) Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
