Andy Ross wrote:
This is really cool, but I'm not a big fan of long function names for simple, global actions. How about we call this thing "print()" and rename the existing print() function (which dumps to the console) log() instead? Almost everyone would prefer this to be the default text output, I think.
I like print() dumping to the console because it does pretty much what you'd expect if you are coming from the C, C++, perl worlds.
Also, rather than copying code from the ATC display, would it be better to unify the two? Is there a really good reason not to have both streams in the same scroll buffer?
It might also be nice to have a version of the display message that takes an X,Y location so you can put message in arbitrary locations.
Curt. -- Curtis Olson http://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
