Don't automatically open Log Viewer on Test Game

The Log Viewer is annoying because it pops up automatically every time you test your game, and you have to manually close it after you're done testing and want to get back to work. Since you're only really going to need it on occasion, why not let the user open it only when they need it?

It's mainly intended to be the default during beta, so you can report errors quicker this way and see what's going on. I'll revert it back to not showing when 3.0 goes gold.

A quick way to dismiss is to press Esc if it's in focus (which it will be after closing the game).

Ahh, alright.

I would love to have dedicated interface button for switching log viewer instead. As well as the ability to bring main Stencyl window on top of the log viewer if possible...

Stencyl 3.0 now seems to be open to everyone, but I see the Log Viewer still automatically loads up, and then has to be manually closed every time you test your game. Please add a function to disable this.

Why not embed it in the background instead of having a separate window for it?

A couple days ago, Jon added a toggle in stencylworks/prefs/boot.txt (ui.logs.autoshow=false) but it doesn't work. I'm sure it'll be fixed soon. Hopefully.

A preference setting would be great, and  - if possible - a public Log4j configuration to allow us to configure the logging itself. But afaik Log4j does exist, but is not used for logging?

Should now be fixed up in the nightlies. I forgot a couple spots.

@Drippple - Correct, we're not using Log4J. It may be included as part of one of the OS libraries we're using.

@Jon: Any chance to refactor to Log4J? Or to expose the logging setup? I have to admit, the Log window is very important, but also annoying in it's behaviour. The simplest fix would be to allow the window to go into the background, means behind Stencyls main window. So we can bring it to front if we really need it.

Can you tell me  where these nightly build are the public release is still 3.0 (B1000) from the download.

The nightlies are available for customers with a subscription.

Hmmm.. I am building this with the demo version but if I cant get this to work properly with the free version I would expect others will be turned off from buying a license.  (there are bugs in the public - random crashes and false errors ) I will be buying it but not until I'm ready to publish. No sense wasting subscription time.

Then just wait until the next public release.  Jon doesn't do public beta testing, and the nightly builds are basically beta versions of upcoming features.