On Sunday 22 March 2009 15:58:27 Melchior FRANZ wrote:
> * Durk Talsma -- Sunday 22 March 2009:
> > 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.
>
> Yeah, I've read that, and we've immediately discussed on IRC how to use
> that. Unfortunately, we didn't have an ATC/Radar screen expert there,
> who could tell us in which way that should appear on the screen.
> One idea would be to put it by where the callsign is now, and only
> if it's not available use the callsign.
Sound good. Just let me know If there's anything that I need to change.
>
> tanker.nas puts the tanker there. It's also artificially (un)intelligent,
> but the main reason for putting it there is that it should be picked
> up by the air-refueling code and radar. And in general, an instrument
> shouldn't get its info via "secret" channels from some other subsystems.
> The property system is for this kind of data exchange. At least this
> was the original design idea.
>
Okay, I though that that might be the case. I've not been following that
discussion too closely, and was assuming that the nasal tanker code would also
make use of the AIModels code, and hence be managed by the AIManager.
FWIW, I don't object against this change, but I am wondering whether it
wouldn't be an idea to integrate the nasal tanker stuff with the existing
AIModels system.
Cheers,
Durk
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
