On Windows, it is not possible to capture the output of the simulator using pipes because the simulator writes stdout to its own private console window. This makes for a bad workflow when using an editor (like Sublime Text 2, Emacs, Vim, etc.) because there is no way for the editor to launch the simulator, capture output, and use the results to track down compilation and runtime errors.
It appears that the Corona Simulator is a Windows *GUI* program that opens a console window for standard output. How about instead making it into a Windows *console* program that opens a GUI window to display the simulator? I suspect this wouldn’t be a substantial change, and would allow programs on Windows to capture stderr/stdout just like the Macintosh version.
This feature change would make the debug cycle much faster because every time a compilation error occurs it can be made to pop up in the editor with the broken line highlighted.
Thanks! [import]uid: 69142 topic_id: 26810 reply_id: 326810[/import]