[Flightgear-devel] Re: property control question

2005-04-07 Thread Melchior FRANZ
* Ampere K. Hardraade -- Thursday 07 April 2005 06:00: On April 6, 2005 05:18 am, Melchior FRANZ wrote: This isn't a big problem and works, too. It's just a waste of CPU cycles and then, you may want to use the gear functions for other effects, where it could be a problem. Something along

Re: [Flightgear-devel] Re: property control question

2005-04-07 Thread Ampere K. Hardraade
On April 7, 2005 03:09 am, Melchior FRANZ wrote: Your standard Nasal key binding skeleton with one commented out line would do (literally) nothing to solve this problem. But maybe I just didn't understand your performance enhancement!? Are you suggesting that we replace all nasal key bindings

[Flightgear-devel] Re: property control question

2005-04-06 Thread Melchior FRANZ
* Josh Babcock -- Wednesday 06 April 2005 04:23: The Superfort's flaps and gear are electrically powered, and the controls for both are instantaneous switches. ie. you have to hold the switch the whole cycle to keep the motor running. Can anyone think of a way to do this? Normally, the g

Re: [Flightgear-devel] Re: property control question

2005-04-06 Thread Erik Hofman
Melchior FRANZ wrote: whereby the stop() method isn't in CVS yet. Which reminded me, now it is. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel

[Flightgear-devel] Re: property control question

2005-04-06 Thread Melchior FRANZ
Here is an improved version. It initializes gear with settimer, because otherwise using /controls/gear could lead to collisions with other parts that messed with it at startup. You can instead use a different property path. And then, we keep SDL's auto-key-repeats from triggering the same function

Re: [Flightgear-devel] Re: property control question

2005-04-06 Thread Andy Ross
Melchior FRANZ wrote: Normally, the g key turns on /controls/gear/gear-down, and YASim watches this property and moves /gear/gear[n]/position-norm accordingly. You just need to override the g/G key bindings in your *-set.xml file: Since this is obviously going to be a common issue, maybe it's

[Flightgear-devel] Re: property control question

2005-04-06 Thread Melchior FRANZ
* Andy Ross -- Wednesday 06 April 2005 17:10: # Slews a property smoothly, without dependence on the simulator # frame rate. [...] If you want to cause motion over time, see # interpolate(). Yes, we want motion over time. slew sets the property only once. So we are again back at

Re: [Flightgear-devel] Re: property control question

2005-04-06 Thread Andy Ross
Melchior FRANZ wrote: Yes, we want motion over time. slew sets the property only once. So we are again back at interpolate()? That's what aircraft.nas does already. Or would you suggest to write a loop that runs as long as the key is held down? Would be slower, wouldn't it? And doesn't

Re: [Flightgear-devel] Re: property control question

2005-04-06 Thread Josh Babcock
Melchior FRANZ wrote: * Josh Babcock -- Wednesday 06 April 2005 04:23: The Superfort's flaps and gear are electrically powered, and the controls for both are instantaneous switches. ie. you have to hold the switch the whole cycle to keep the motor running. Can anyone think of a way to do this?

Re: [Flightgear-devel] Re: property control question

2005-04-06 Thread Josh Babcock
Andy Ross wrote: Melchior FRANZ wrote: Normally, the g key turns on /controls/gear/gear-down, and YASim watches this property and moves /gear/gear[n]/position-norm accordingly. You just need to override the g/G key bindings in your *-set.xml file: Since this is obviously going to be a common

Re: [Flightgear-devel] Re: property control question

2005-04-06 Thread Ampere K. Hardraade
On April 6, 2005 05:18 am, Melchior FRANZ wrote: Here is an improved version. It initializes gear with settimer, because otherwise using /controls/gear could lead to collisions with other parts that messed with it at startup. You can instead use a different property path. And then, we keep