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. Obviously, the final say will be Curt's, but I'm going to insist as hard as I can that we have the mouse code provide Euler angles like all the other input sources. 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). All the best, David -- David Megginson [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
