Re: FlightGear 2016.3.1 [Rio]
Posted: Tue Sep 13, 2016 7:58 pm
The console was changed because FGRun would crash if an aircraft caused error messages.
It's a lot harder than it seems to make the console work reliably under Windows than you'd imagine. The old way had problems too; such as an exception being printed and then the window immediately closing making it a game of reflexes to try and get a screen capture to see the message.
Ideally Windows would just work like it does in unix; that way you could see the errors, redirect to a log file, or less.
I've got some Win32 code somewhere that worked reasonably well opening a console from a "GUI" application; but I can't find it and it took me a long time to get it right when I did it.
Personally I've given up with launchers for development and just make a batch file to do the necessary; it's much faster and now I get to see all of my errors. FGRun is great at giving you the command line arguments to use.
It's a lot harder than it seems to make the console work reliably under Windows than you'd imagine. The old way had problems too; such as an exception being printed and then the window immediately closing making it a game of reflexes to try and get a screen capture to see the message.
Ideally Windows would just work like it does in unix; that way you could see the errors, redirect to a log file, or less.
I've got some Win32 code somewhere that worked reasonably well opening a console from a "GUI" application; but I can't find it and it took me a long time to get it right when I did it.
Personally I've given up with launchers for development and just make a batch file to do the necessary; it's much faster and now I get to see all of my errors. FGRun is great at giving you the command line arguments to use.