* Gerard Robin -- Wednesday 22 June 2005 18:46:
> Le mercredi 22 juin 2005 à 16:44 +0200, Gerard Robin a écrit :
> > If i need to keep the old process, what must be done on my side ?
> In addition to my previous question which is waiting for an answer.
I thought I had answered that by underlining this part: "exactly behave
as before". I'll try again: the behavior is exactly the same as before!
There's nothing that you have to change to get exactly the same as before.
But now you *can* redefine the wrapper. Why is this useful?
BEFORE:
kbd binding----------------------------------\
|----> property
js binding-----------------------------------/
NOW (and since a while for flaps and many others):
kbd binding--------\
controls.gearDown()-----------> property
js binding---------/
If you wanted something else than default behavior, you had to redefine
the keyboard bindings. That's done by many aircraft, and in many cases
the right thing to do. But it's bad for control functions that people
typically have on their joysticks, and not on standardized buttons, but
wherever the driver author felt like. There simply was no way to
redefine js functions in a sane way. NOW, an aircraft with special needs
just overrides the wrapper function in controls, and keyboard *AND*
js button functions remain intact.
And this is by no means innovative. Andy had done this for several
control functions already. Just a few were/are missing. What is "new"
is the fact that the default bindings for gear and flaps do now also
report key/button release. This is required for gear/flaps without
defined 'notches', that can stop anywhere during movement. An overriding
function *can*, but doesn't *have* to use this information. The default
wrapper doesn't. The b29's maybe will. (The Hurrican doesn't either. :-)
> Is it any consequence when using <interpolation> ?
No. The behavior is *exactly* the same as before. The aircraft.door()
class does all the necessary stuff using interpolate() already. But you
are free to re-invent that wheel.
m.
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
