Norman Vine writes: > 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
I want my normal view 20% slightly to the left. I can set this with the mouse. I can now use the keys to spin about, and when I'm done I'm back at my normal position. I want my normal view 20% slightly to the left. I can set this with the joystick. I can now use a python script over the HTTP interface to spin about, and when I'm done I'm back at my normal position. I want my normal view 20% slightly to the left. I can set this with my graphics tablet. I can now my joystick hat to spin about, and when I'm done I'm back at my normal position. etc. I think it's fundamental wrong to make a special case for the mouse -- it breaks encapsulation (i.e. some of the view math gets moved out of the viewer) and forces everyone to do things two different ways. > 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 :-) This would be a stack-based approach for the viewer, not for the user input modes. In fact, with the property module, it is extremely easy to push and later restore any subbranch of the property tree -- someone just has to figure out the user interface for it. All the best, David -- David Megginson [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
