Some way to silence most of the output
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
widelands |
Won't Fix
|
Low
|
Unassigned | ||
widelands (Debian) |
Fix Released
|
Unknown
|
Bug Description
When running WL from the terminal it outputs a lot of information during the game. It might be useful for debugging issues, but a lot of it seems unnecessary for regular users, and could probably be silenced. Alternatively, we could split the messages into the usual levels (error, warning, info, debug) and only print errors+warnings unless more information is specified. This would keep the amount of output low for normal users but would give developers/
(As a side-note; the combat messages gives you information you may not have access to in the game, but I don't know if there is a way to gain an advantage of this except being able to tell that there is a fight going on somewhere on the map.)
This has been requested earlier (see the bug in Debian), but I was reminded of when I saw the amount of output we get with the new caching system in place. Regardless I think it is nice to forward the request upstream to get a final answer, rather than it being stuck in the Debian BTS.)
Related branches
- SirVer: Approve
-
Diff: 34 lines (+0/-5)2 files modifiedsrc/logic/replay.cc (+0/-2)
src/logic/trainingsite.cc (+0/-3)
Changed in widelands (Debian): | |
status: | Unknown → Confirmed |
Changed in widelands (Debian): | |
status: | Confirmed → Fix Released |
Those debug outputs should probably just be removed, or perhaps commented / #ifdef'd out in the code. In the case of the caching code, it could perhaps be reduced to some kind of warning if surfaces are evicted after less than X seconds.
At the end of the day, the debug output from random bug reports doesn't tend to be very useful. At least in the game logic, I always tend to just analyse what happens and then throw in very analysis-specific log output.