Re: [Flightgear-devel] JSBSim Functions for Propwash and Downwash [was: Clarification on YASim input]

2011-06-20 Thread Hal V. Engel
On Sunday, June 19, 2011 09:58:48 AM Bertrand Coconnier wrote: > 2011/6/19 Ron Jensen : > > On Saturday 18 June 2011 21:00:41 Jon S. Berndt wrote: > >> Here's an example from Hal's P-51D Mustang. This is from an old version, > >> so it may have changed by now, but it illustrates the approach. In th

Re: [Flightgear-devel] Heads up: scenery download / built-in

2011-06-20 Thread Vivian Meazza
I wrote: > > ThorstenB wrote: > > ... snip ... > > > > So, I am really sorry, Vivian, that you were still unable to make the > > system work for you - on day 2 (though it seems people only started > > trying to use it _today_). > > > ... snip ... > > Getting back to the original purpose ... it'

Re: [Flightgear-devel] FlightGear development entered state

2011-06-20 Thread James Turner
On 20 Jun 2011, at 21:52, Martin Spott wrote: > This is the first time we're aiming at having one release every six > months and not everything will be perfect on the first attempt. Anyhow > I'm still proposing to let us familiarize ourselves with the > implications of having a release plan inste

Re: [Flightgear-devel] FlightGear development entered state

2011-06-20 Thread Martin Spott
Stuart Buchanan wrote: > I don't think there's a convincing reason why it can't wait until the next > development cycle, but I was unclear as to whether aircraft were > considered major features. Ah, well, aircraft are a pretty prominent feature in flight simulation, don't they ;-) While we're

Re: [Flightgear-devel] FlightGear development entered state

2011-06-20 Thread Stuart Buchanan
On Mon, Jun 20, 2011 at 9:52 PM, Martin Spott wrote: > Comments on the state of the c172 model went unheard for months, > therefore I'd like to hear a really convincing reason why such major > overhaul can't wait until the tree is open for the next development > cycle. Not quite unheard - just inc

Re: [Flightgear-devel] FlightGear development entered state

2011-06-20 Thread Gijs de Rooy
Hi all, > Stuart wrote: >> Both of the changes in question are major model overhauls to the respective > models (c172p, c150). I need to correct that slightly. "All" I've been working on is a (c172p) new panel including the pedestal. There were a lot of faults and missing switches in the previo

Re: [Flightgear-devel] FlightGear development entered state

2011-06-20 Thread Martin Spott
Hi Stuart, Stuart Buchanan wrote: > Both of the changes in question are major model overhauls to the respective > models (c172p, c150). Comments on the state of the c172 model went unheard for months, therefore I'd like to hear a really convincing reason why such major overhaul can't wait until

Re: [Flightgear-devel] FlightGear development entered state

2011-06-20 Thread James Turner
On 20 Jun 2011, at 21:18, Stuart Buchanan wrote: >> No, not generally. Obvious fixes are ok, major overhauls are not, in >> case of doubt I'd propose that the changes in question should be >> reviewed (which is a darn good idea anyway ;-) > > Well, I _was_ planning to review the changes. :

Re: [Flightgear-devel] FlightGear development entered state

2011-06-20 Thread Stuart Buchanan
On Mon, Jun 20, 2011 at 9:11 PM, Martin Spot wrote: > Stuart Buchanan wrote: >> On Fri, Jun 17, 2011 at 8:47 PM, Torsten Dreyer wrote: > >>> Please refrain from pushing new features or major infrastructure changes >>> to our streams. Please note: this includes fgdata, too! > [...] >> What's the po

Re: [Flightgear-devel] FlightGear development entered state

2011-06-20 Thread Martin Spott
Stuart Buchanan wrote: > On Fri, Jun 17, 2011 at 8:47 PM, Torsten Dreyer wrote: >> Please refrain from pushing new features or major infrastructure changes >> to our streams. Please note: this includes fgdata, too! [...] > What's the position on aircraft updates? They're part of "fgdata" ;-) Ind

Re: [Flightgear-devel] FlightGear development entered state "feature-freeze" until July, 17th 2011

2011-06-20 Thread Stuart Buchanan
On Fri, Jun 17, 2011 at 8:47 PM, Torsten Dreyer wrote: > Short version for the impatient reader: > Please do _NOT_ push any major changes or new features to simgear, > flightgear, fgdata until further advice! > Please refrain from pushing new features or major infrastructure changes > to our str

Re: [Flightgear-devel] Nasal updating properties in the menu

2011-06-20 Thread Hal V. Engel
On Sunday, June 19, 2011 05:12:31 PM Ron Jensen wrote: > On Sunday 19 June 2011 17:55:25 Hal V. Engel wrote: > > On Sunday, June 19, 2011 02:15:54 PM Ron Jensen wrote: > > > http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg3 > > > 02 > > > > > >08 .html gui.menuBind("radio", "d

Re: [Flightgear-devel] JSBSIm, aeromatic, crosswind taxiiing, et cetera

2011-06-20 Thread Ron Jensen
On Sunday 19 June 2011 10:50:01 John Denker wrote: > On 06/19/2011 06:46 AM, Jon S. Berndt wrote: > > Maybe I've gone wrong somewhere here, but something similar might work. > > Also, in situations like a flat spin or tail slide this probably falls > > apart! > > Let's postpone discussion of exotic

Re: [Flightgear-devel] Nasal updating properties in the menu

2011-06-20 Thread Vivian Meazza
Hal, Works nicely here - I've just pushed an update into the TR1133.nas file This is the line: gui.menuBind("radio", "TR1133.radio_dlg.open()"); You should be able to adapt that to the SC-522 Vivian -Original Message- From: Hal V. Engel [mailto:hven...@gmail.com