-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clicking on a log doesn't jump to the code line but to ForwardToUnity() - Unity 2019.2.1 #52
Comments
Note: when I click on the log with the standard Console, it goes to the line specified above. If I click on it with Uber Console, nothing happens (it used to work in the previous Unity 2018). |
Did you find a solution now? I have the same problem. |
No :( |
Hi! Sorry for the delay - I can look at this at some point. I suspect it's nothing too difficult to fix. |
Is there any update on this issue? |
Replace line 751 in UbberLoggerWindow.cs with this : |
I can confirm that this fix is working for me on Unity 2019.2.6f1 on Windows 10. |
We recently upgraded from Unity 2018 to 2019.2.1. Before, when I clicked on a log, it used to go to the line in the code. Now it goes to
else if(severity==LogSeverity.Error) UnityEngine.Debug.LogError(showObject);
instead`[LogUnityOnly()]
static void ForwardToUnity(UnityEngine.Object source, LogSeverity severity, object message, params object[] par)
{
object showObject = null;
if(message!=null)
{
var messageAsString = message as string;
if(messageAsString!=null)
{
if(par.Length>0)
{
showObject = String.Format(messageAsString, par);
}
else
{
showObject = message;
}
}
else
{
showObject = message;
}
}
We are using a simple "middleman" class called CustomDebug:
`public static class CustomDebug
{
}`
The text was updated successfully, but these errors were encountered: