Thanks , I have too many tests running, making errors go by too fast to see
... , missed that one ...
> Nasal runtime error: undefined symbol: set_barber_pole
>
> at /opt/FlightGear/FlightGear_cvs/data/Aircraft/b1900d/Nasal/systems.nas,
> line 132
> called from: /opt/FlightGear/FlightGear_cvs/da
On Fri, 2010-03-12 at 18:55 -0800, syd adams wrote:
> Hi guys ,
> This is another patch for the overspeed
> It keeps the overspeed properties out of property tree when airspeed
> indicator is not 'overspeed ' enabled
> No sense putting unused properties in an already heavily populated
>
Thanks James
On Sat, Mar 13, 2010 at 4:24 AM, James Turner wrote:
>
> On 13 Mar 2010, at 02:55, syd adams wrote:
>
> > Could someone apply please ?
>
> Done.
>
> James
>
>
>
> --
> Download IntelĀ® Parallel Studio Eval
>
On 13 Mar 2010, at 02:55, syd adams wrote:
> Could someone apply please ?
Done.
James
--
Download IntelĀ® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-
Hi guys ,
This is another patch for the overspeed
It keeps the overspeed properties out of property tree when airspeed
indicator is not 'overspeed ' enabled
No sense putting unused properties in an already heavily populated property
tree .
Could someone apply please ?
Thanks .
? airspeed
5 matches
Mail list logo