search

google-code-export / bwapi

Automatically exported from code.google.com/p/bwapi
0 stars 0 forks source link

dedicated log tool #177

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Problem:
Logging is needed.... practically never. And logging to a file at a path 
from an .ini file is not a fast nor handy solution.

Solution:
A dedicated tool. You run the tool (an .exe) and then every log message 
produced in BWAPI will be logged into the tool's window. 3 Buttons 
featuring "Clear log", "Save log", "Load log" and some check boxes for the 
log view's filter. And when the program is not running, the log messages 
won't even have to be generated, not slowing BWAPI down.

Technical:
With our Util set, pipe communication (especially when there is only one 
type of packet) is as straightforward as writing to a file but a lot 
faster and a lot more user-friendly.

Open for bashing.. now!

Original issue reported on code.google.com by goo...@teabix.com on 1 Jan 2010 at 10:16

GoogleCodeExporter commented 9 years ago 
another alternative is to remove logging. BWAPI can be run in debug mode now so 
is 
it worth the extra lines of code?

Original comment by goo...@teabix.com on 3 Jan 2010 at 12:16

GoogleCodeExporter commented 9 years ago 
current logging system is sufficient.

Original comment by lowerlo...@gmail.com on 20 Jun 2010 at 12:53