Editor Console Clickable Link Improvement

[manutoo]

Hello,

it’d be nice if I could inject clickable source links in my own Debug.Log() messages.

eg: I use try{} catch {} to catch most exceptions in my code, so the clickable links are never to where the bugs actually happen.

[Xarbrough]

I use wrapper classes for logging and also a few systems such as scene validation which logs errors when checking the scene. It’s nice that I can pass a context object which will be highlighted, when single-clicking the log statement in the console, but it would be even better if I could double click the log statement to jump to a specific line in source code.

[Peter77]

I also wrote feedback regarding the editor console a while ago:

Editor Console Improvements, double-click message functionality

Editor Console Improvements, double-click message functionality

I just read on your 2019.1 blog-post: [quote] The editor console has been updated with clickable stack trace links that will take you to the source code line for any function calls listed in the stack, and textual search to filter down your console entries. [/quote] https://blogs.unity3d.com/2019/01/31/unity-2019-1-beta-is-now-available/ I have a related question. We discussed having the ability to exclude methods from the stacktrace in June 2015 on the Unity beta group: https://groups.go…

[DrummerB]

@Xarbrough_1

I use wrapper classes for logging and also a few systems such as scene validation which logs errors when checking the scene. It’s nice that I can pass a context object which will be highlighted, when single-clicking the log statement in the console, but it would be even better if I could double click the log statement to jump to a specific line in source code.

If you put your wrapper classes in a separate managed DLL, you can fix the double click behavior. I submitted a feature request about this a while ago here .