[Flightgear-devel] Re: Nasal controls.nas patch for multi-engine aircraft and changes to C310
* Martin Spott -- Friday 03 March 2006 09:12: would you mind taking into account that we (hopefully) someday will have carburator heating for certain piston-engined aircraft being modelled in Flightgear ? We'll take that into account once it was (hopefully) implemented in certain piston-engined aircraft some day. That's soon enough. m. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Nasal controls.nas patch for multi-engine aircraft and changes to C310
Melchior FRANZ wrote: * Martin Spott -- Friday 03 March 2006 09:12: would you mind taking into account that we (hopefully) someday will have carburator heating for certain piston-engined aircraft being modelled in Flightgear ? We'll take that into account once it was (hopefully) implemented in certain piston-engined aircraft some day. That's soon enough. Sorry, you don't understand: I was suggesting to take that into account _now_ in order to avoid future reshuffling the keyboard layout once you realize that carb heating would be best placed close to throttle and mixture settings Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Re: Nasal controls.nas patch for multi-engine aircraft and changes to C310
* Martin Spott -- Friday 03 March 2006 10:43: Melchior FRANZ wrote: We'll take that into account once it was (hopefully) implemented in certain piston-engined aircraft some day. That's soon enough. Sorry, you don't understand: I understood you perfectly fine. But you didn't understand me. m. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Re: Nasal controls.nas patch for multi-engine aircraft and changes to C310
* Buchanan, Stuart -- Friday 03 March 2006 10:30: --- Melchior FRANZ wrote: Makes sense to me. (The implementation less so. :-) Well, to be consistent I was copying code from elsewhere in the Nasal file. ... just not the placing of parentheses. :-P I assume you have some way of doing this in half the number of lines :) That's not the main issue. You are using the indices of a Nasal array as property indices. But properties aren't guaranteed to be continuous. You could have engine[3] and engine[7], and no engine[0] etc. (Even though nobody would probably do that.) Besides that, IMHO foo += 1 should be preferred to foo = foo + 1. In the latter case one has to check if the variables are really the same. Easy for i or foo, but less so with longer variable names. And finally, this for(i=0; isize(engs); i=i+1) can be written as forindex (i; engs) Not that shorter is necessarily better, of course. But again, those last two points were not what I found to make less sense. Makes sense, too, but I wonder if we shouldn't assign that globally in keyboard.xml. Looking into map.pdf I see that n/N has no meaning per default, but several aircraft defining it to mean the same: a) Obviously this function only applies to some aircraft. I haven't checked the effect of adjusting the prop on, say the c172 or j3cub. True. But it applies to more aircraft than select engine 4 or decrease spoilers. b) Some people are a bit concerned about using up all the keyboard assignments (though presumably they can be over-written in an aircraft .xml file?) I'm usually concerned, too. But here we have 7 aircraft that use n/N for propeller pitch already, and some are still missing (pa24, pa28, aerostar, b29, ...?). There are a few dozens of keys still unassigned (almost all Alt bindings), some could be removed or put into extra files (like it was done with the carrier keys) or dialogs. Living with unassigned key bindings doesn't buy us much, either. Using them makes sense, wasting them does of course not. m. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Re: Nasal controls.nas patch for multi-engine aircraft and changes to C310
* Buchanan, Stuart -- Thursday 02 March 2006 20:11: I have a patch to Nasal/controls.nas. The patch changes the adjEngControl() function to apply the adjustment to the currently selected engine, rather than all of them. This directly affects adjThrottle(), adjMixture(), adjCondition() and adjPropeller(). Makes sense to me. (The implementation less so. :-) I also have a patch to the C310 so that the propeller control repeats, available from http://www.nanjika.co.uk/flightgear/c310-set.diff Makes sense, too, but I wonder if we shouldn't assign that globally in keyboard.xml. Looking into map.pdf I see that n/N has no meaning per default, but several aircraft defining it to mean the same: N (78) c182|c182-2dpanel|c310|c310dpm-3d|hurricaneIIb|seafireIIIc|spitfireIIa: Propeller Coarse n (110) c182|c182-2dpanel|c310|c310dpm-3d|hurricaneIIb|seafireIIIc|spitfireIIa: Propeller Fine m/M is mixture already, and right beside n/N. m. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
