Andy Ross <[EMAIL PROTECTED]> said: > > It is not mutable by anything but the mouse code. I want a hat swtich > to change view direction. This is not even vaguely possible with the > current implementation (especially if you refuse to read properties > from the mouse code -- properties are all the hat switch mapping can > set). > Yes, the mouse input needs to be seperated from the view code, no one disagrees.
> Could the features be gotten by augmenting and modifying your code? > Surely; but my reasonably well-informed opinion is that it would be > less work to start from scratch. I'm sorry that the general consensus > seems to be to eject your code; really I am. But it just isn't useful > to a lot of us. Neither is the view-offset/view-tilt stuff, for that > matter. We need something new. > Andy there's nothing unique about this situation. This has grown piece by piece and it is time to rebuild the view stuff. Norm's been telling us this, so the polite thing to do would be to read the list and tone down the attack. From where I sit, Norm's work is excellent...and I agree with Dave that we need to preserve his optimizations when possible. Where he's just thrown in something as a temporary patch (aka idea), he generally notes it in the code. Now its time to go back and clean it all up. Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
