Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/Instrumentation agradar.cxx, 1.3, 1.4 rad_alt.cxx, 1.2, 1.3 wxradar.cxx, 1.28, 1.29 wxradar.hxx, 1.20, 1.21

[Durk T. <d.t...@xs...>]

Hi,

On Tuesday 17 March 2009 23:01:38 Melchior Franz wrote:
> Update of /var/cvs/FlightGear-0.9/source/src/Instrumentation
> In directory baron.flightgear.org:/tmp/cvs-serv17937/src/Instrumentation
>
> Modified Files:
> 	agradar.cxx rad_alt.cxx wxradar.cxx wxradar.hxx
> Log Message:
> wxradar: read aircraft data from the property tree, rather than AIBase
>
> This allows to display objects that are in /ai/models/, but not managed
> by the AI manager, and it follows fgfs' design principle that subsystems
> should communicate over the property tree (if possible). This is a tad
> slower, but the radar is only updated once every second.
>

FWIW, I just checked in a small change that allows the AI Air Traffic 
controller to request the AI Aircraft to set a squawk code. The actual 
assigned code is written to the property tree and could therefore be used by 
the radar code for display purposes. For now, I've bound the actual code to 

/ai/models/aircraft[x]/transponder-id

I'm open to suggestions for a more appropriate location in the property tree 
if that is deemed necessary.

BTW: What are "objects that are in /ai/models/ but not managed by the AI 
Manager? All the properties that are written to /ai/models  are part of the 
AIModels subsystem, (including multiplayer aircraft) and consequently managed 
by the AI Manager, or am I missing something?

Cheers,
Durk