Added logging priorities and use SDLs logging facilities

By using SDL logging, we can rely on SDL to filter the log messages by
their priority before they get sent to our custom output function. For
example, we now no longer get entries for created and destroyed Window
instances by default, since these have only "debug" priority whereas the
default priority for the "app" category is "info".

We can also get log messages raised by SDL itself in our log now. Log
levels can be controlled per category through the "SDL_LOGGING"
environment variable.

Many existing log messages have been assigned a category based on their
existing prefix.

1 files changed, 2 insertions, 2 deletions

diff --git a/src/net/manaserv/effecthandler.cpp b/src/net/manaserv/effecthandler.cpp
index 22d1f9cf..afd7cd5c 100644
--- a/src/net/manaserv/effecthandler.cpp
+++ b/src/net/manaserv/effecthandler.cpp
@@ -82,7 +82,7 @@ void EffectHandler::handleCreateEffectBeing(MessageIn &msg)
     if (b)
         effectManager->trigger(eid, b);
     else
-        logger->log("Warning: CreateEffect called for unknown being #%d", bid);
+        Log::warn("CreateEffect called for unknown being #%d", bid);
 }
 
 void EffectHandler::handleCreateTextParticle(MessageIn &msg)
@@ -120,7 +120,7 @@ void EffectHandler::handleShake(MessageIn &msg)
             viewport->shakeScreen(intensityX, intensityY, decay, duration);
             break;
         default:
-            logger->log("Warning: Received GPMSG_SHAKE message with unexpected length of %d bytes", msg.getUnreadLength());
+            Log::warn("Received GPMSG_SHAKE message with unexpected length of %d bytes", msg.getUnreadLength());
     }
 }