* gerard robin -- Thursday 19 March 2009: > Then, do you mean that the old "Radar Fashion" will be removed, > what a pity.
I haven't planned that (yet). But in the long run it should get removed. This was an early mechanism to get the brand-new AI models on the screen (for the T38?), and that was OK back then, and a nice new feature. But it's simple and unrealistic and just doesn't fit in our framework. A radar needs to be a regular instrument -- and the wxradar is just that. Or it should be some customized Nasal logic like in the f-14b. New AI objects like the tanker shouldn't have to generate absurd values to emulate that obsolete radar. That would only prolong its lifetime. That's inhuman. :-) But you can easily generate shift-x/shift-y etc. for the radar you are actually using. Your aircraft knows which radar that is. The tanker doesn't know that. It's like demanding that the tanker decides whether your gear is extended or retracted. It just doesn't know. > It is very useful. We could want to keep it . Did you have a look at the wxradar? You can check out the ufo. Press Shift-p to enable the radar screen and Ctrl-c to see the click-sensitive areas. Unfortunately, there are no button labels. Clicking on the two range numbers increases/decreases the range. You don't need any Nasal for that radar type, and you can select radar shadows, symbols, and (once re-implemented) cloud shadows. m. ------------------------------------------------------------------------------ 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
