[Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/Instrumentation kt_70.cxx, 1.1, 1.2

2005-01-05 Thread Roy Vegard Ovesen
Curt, See this discussion between David M. and me about setting property values in source code vs. setting them in config files. http://baron.flightgear.org/pipermail/flightgear-devel/2004-November/031882.html After this I removed all set serviceable property to true from instrumentation and

Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/Instrumentation kt_70.cxx, 1.1, 1.2

2005-01-05 Thread Curtis L. Olson
Roy Vegard Ovesen wrote: Curt, See this discussion between David M. and me about setting property values in source code vs. setting them in config files. http://baron.flightgear.org/pipermail/flightgear-devel/2004-November/031882.html After this I removed all set serviceable property to true

Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/Instrumentation kt_70.cxx, 1.1, 1.2

2005-01-05 Thread David Megginson
On Wed, 05 Jan 2005 08:01:49 -0600, Curtis L. Olson [EMAIL PROTECTED] wrote: So what's the solution? We can't initialize any number of arbitrary serviceable properties in the preferences.xml and I've always been nervous about doing htat anyway. If we also can't do it in code, then were are

Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/Instrumentation kt_70.cxx, 1.1, 1.2

2005-01-05 Thread Roy Vegard Ovesen
On Wednesday 05 January 2005 15:26, David Megginson wrote: On Wed, 05 Jan 2005 08:01:49 -0600, Curtis L. Olson [EMAIL PROTECTED] wrote: So what's the solution? We can't initialize any number of arbitrary serviceable properties in the preferences.xml and I've always been nervous about