what to do with about printing to much?
← Thread:User talk:Beaming/what to do with about printing to much?/reply (7)
I don't think Robocode exposes anything about the environment (app vs control API, graphics or not). You can tell if graphical debugging is enabled, though, because onPaint() will be called. You could use that as your debug switch. I mainly use graphical debugging and log severe stuff to file.
As for X11, I don't know, I would guess it's due to using some java.awt code internally or something. I have run RoboRumble over a terminal quite a bit, but maybe my terminal has the X stuff setup. (Mac OS X Terminal connecting to Ubuntu.)
Unfortunately, RoboRunner seems to suffer from the same issue.
Set DISPLAY variable to something crazy and run RoboRunner you will see it crush as well.
Try adding the "-Djava.awt.headless=true" parameter to how you invoke Java. I believe that does the trick. I seem to recall once trying this in the past.
This helps with rumble clients, so it probably good idea to ping developers about this switch to be on by default.
However, it does not help with RoboRunner.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page.
Return to Thread:User talk:Beaming/what to do with about printing to much?/reply (12).