koobas.hobune.stream
Debug.Log Override?
Is it possible to change the Debug.Log void and if so is anything like this close:
using UnityEngine;
using System.Collections;
public class Debug : MonoBehaviour {
public override void Log (string debugMsg) {
base.Log ();
var example = "Hey";
}
}
Debug.Log is a static method, so you can't override it. You also can't create Static Extension methods, Extension methods only work on instances.
You could create your own Logger class with it's own Static logging functionality which has the improvements you want. There are even some of these on the asset store.
I'm not sure what you're trying to do with that example.
I really simply want to catch all errors/debugs and log them to a file. I got the log to file working, I only need to get the logging, and Application.RegisterLogCallback() only catches errors/debugs on the script it is attached to.
It shouldn't. You are registering it with the Application itself, it should trap any logs called.
Apparently there's an issue with only trapping logs on the same thread however. It may be that you are only seeing logs from the script it's being attached to because of threading issues.
http://docs.unity3d.com/ScriptReference/Application.RegisterLogCallbackThreaded.html
I am not using multiple thread (Excepts for A* which is using multithreading if I am not mistaking) But all the other scripts is on the same thread.
I am registering it like this:
void Start(){
Application.RegisterLogCallback(Logger);
}
And the logger function looks like this:
public void Logger(string text, string stackTrace, LogType type) {
Game.LogToFile(text);
if (type == LogType.Error || type == LogType.Assert) {
$$anonymous$$essageForLog = text;
}
}
And Game.LogToFile never gets called so it isn't getting longer than this. (Apart from when I run a debug.log on the current script.
FYI RegisterLogCallback is now deprecated.
Now, you want to use the event:
Application.logMessageReceived += HandlerMethodName;
The handler signature must be: HandlerMethodName(string logString, string stackTrace, LogType type)
I found the bug, you have to call Application.RegisterLogCallback in the same frame as the Debug.Log is called :)
