Le mercredi 22 juin 2005 à 16:03 +0200, Melchior FRANZ a écrit :
> The joysticks and default keyboard bindings do no longer set the gear/flap
> properties directly, but both use wrapper functions in controls.nas. The
> flaps did this since a while, but behave differently now: The bindings don't
> only report flaps/gear up/down, but also when the button was released. The
> default "controls" functions ignore this additional information and should
> exactly behave as before. But aircraft can now easily redefine the "controls"
> functions to implement aircraft specific gear/flaps handling. Redefining
> key/button bindings broke all input device configs, while redefining the
> wrapper functions lets every js/kbd function where it used to be.
>
> To make the gear only move while "g"/"G" is pressed (or the gear buttons
> on the js), and immediately stop movement on release, define for example this
> in, let's say b29.nas:
>
> gear = aircraft.door.new("/controls/gear", 10); # 10 seconds for full
> move?
>
> controls.gearDown = func {
> if (arg[0] < 0) {
> gear.close();
> } elsif (arg[0] > 0) {
> gear.open();
> } else {
> gear.stop();
> }
> }
>
> Of course, the use of the aircraft.door class isn't mandatory. But it's
> quite convenient. The moving door property is in /controls/gear/position-norm.
>
> m.
>
If i need to keep the old process, what must be done on my side ?
Thanks
>
--
Gerard
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
