My favorites | Sign in
Project Home Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 157: trace() should systematically flush the stdout buffer
1 person starred this issue and may be notified of changes. Back to list
Status:  WontFix
Owner:  ----
Closed:  Apr 2012


 
Reported by tyn...@gmail.com, Feb 20, 2012
What steps will reproduce the problem?
1. Uses FlashDevelop, which displays the stdout.
2. Create an empty project with a main() function.
3. In this function, simply call trace("test");
4. Starts the program.
5. Nothing appears in the 'Output' window yet.
6. Close the program: the trace appears in the 'Output' window.

What is the expected output? What do you see instead?
The trace() statement should flush the stdout buffer, and the text shall appear in the 'Output' window right as 'trace' is called.
Feb 23, 2012
Project Member #1 gameh...@gmail.com
Hi
(Using 4.01) I see a command window with the correct trace in it, followed by "Press any key to continue".  Is there something else to look for?

Hugh

Feb 23, 2012
#2 tyn...@gmail.com
Hello!

Using NME (last version) + HXCPP (last version) + FD (4.01), I don't see a command window. Instead, I see an empty rendering window, and the console output displayed in a pane named "Output" integrated inside FlashDevelop.

Maybe it's an NME issue then?
Mar 15, 2012
Project Member #3 gameh...@gmail.com
Hi,
There is a "no_console" setting that is set by NME by default.  You can put this in your nmml:

<set name="SHOW_CONSOLE" value="1' />

Hugh
Apr 8, 2012
Project Member #4 gameh...@gmail.com
Hi,
I think this is an NME problem with sdl.  And joshua has a solution, so I'm going to close this issue here.
Status: WontFix

Powered by Google Project Hosting