Loading Console Window

[Slugger]

In the middle of writing a loadable class and hitting a bit of a bug (in my code) and really need the console window so I can println() some variables to see what's going on. I added the 'consolewin' dword value to the registry and set it to one, stopped and restarted the SageTV service, but I don't see a console window.

I'm still using the trial version of Sage6, is this what's preventing me from seeing the console window by any chance? Thought I'd ask before replacing all my System.out.println() calls with file I/O calls to see my vars.

[nielm]

The Service cannot create a console window.... If your class really needs to be in the server, run Sage in non-service mode.

Otherwise put it in the client...

[GKusnick]

I agree with Niel. Don't run untested code in your service. Debug it in a client first (or if you have no client licenses, in a pseudo-client running on your server).

Alternatively, enable SageTV's native debug logging in your service and consult the log files it produces. No need to create a separate log file for your code (unless you want to).

Or if you want to monitor your running service in real time, send your println() output to a Writer that wraps the OutputStream of a Telnet socket.