* John Denker -- Sunday 04 March 2007: > It would be necessary to deal with the fact that there can be N different > "ATC" messages tuned up at the same time,
Whereby all are spoken with the same voice, and all are printed to the single one terminal. Using a single message property wouldn't make the situation any worse. But, OK, let's keep it in the /instrumentation/*/atis property, with a reduced chance of it appearing somewhere. Because, again, it won't be printed to the terminal by default. Unless Curt rules that it be there, basically abandoning the logging system. > 2) Even if it worked, such code would be undesirable ... because the > idea of receiving a textual ATIS during flight is unrealistic, I'm not sure if you just didn't get what I wrote, or if you are intentionally misrepresenting it to make your point stronger. I wrote: * Melchior FRANZ -- Sunday 04 March 2007: > Everyone interested in having the ATIS messages > in the terminal can then [...] > Or add this to have the ATIS messages printed on top of the screen: Can you understand that? "everyone interested *can*"? As opposed to your "cout" that forces this on everyone without possibility to avoid it. The rest of your counter argument is based on your wrong assumption and thus void. Sigh, I give up. m. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
