Ability to Ignore a Specific Method When Double-clicking on a Console Log

Scripting
,
1

In 2022.2, you added the ability to hide methods from the console callstack.

So this code

public class TestScript : MonoBehaviour
{
    private void Start()
    {
        SomeMethodNotShownInConsole();
    }

    [HideInCallstack]
    public void SomeMethodNotShownInConsole()
    {
        Debug.Log("Hey!");
    }
}

will appear like this
8649555--1163715--upload_2022-12-9_17-25-3.png

This is really nice, but I’d like to something more. When the user double clicks on the log, I’d like Unity to ignore some methods. This would allow us to develop our own logging wrappers without breaking the UX.

For example:

public class TestScript : MonoBehaviour
{
    private void Start()
    {
        MyLogSystem.Log("Hello!");
    }
}

public static class MyLogSystem
{
    [HideInCallstack]
    public static void Log(string message)
    {
        Debug.Log(message);
    }
}

If the user double clicks on the “Hello!” log, they will be sent at line 14 inside MyLogSystem class, even if this method is hidden. I’d like to send the user to line 5 instead, at the real log instigator.

This issue severely impacts the UX of the console when working with custom logging wrappers. All the commercial Unity projects I’ve been on were using this paradigm and it was a pain to lose the double-click feature.

Should this requested “skip method on double-click” be part of the [HideInCallstack] attribute or should it be it’s own attribute? I don’t know.

8649555--1163712--upload_2022-12-9_17-24-32.png

2

In case someone stumbles on this thread when trying to find solution to this problem, I explained how I overcame it in this thread: How about getting HideInCallstack to work right?

4

Actually it doesn’t work at all for me anymore (2022.2.18f1).
Here is the documentation for that attribute: Unity - Scripting API: HideInCallstackAttribute poor bunny

5

What do you mean by “it”? The OP asked a question how to solve the issue that the double click does not end up where it should be and that “HideInCallstack” just hides the method in the callstack. Or do you mean by “it” the solution that @Theromanek100 mentioned? When you bump on old thread you should give more information what you actually talk about. Does the “Logger.Log” trick that was mentioned in the linked thread still work or is that was you’re complaining about?

6

Uhm, you still haven’t said what doesn’t work. You do realise that this question asked how to solve the double click issue which has nothing to do with hiding a method call in the callstack. The HideInCallstack attribute should only hide this method in the stacktrace of the log entry. It doesn’t change anything about the double click behaviour. That’s what the question was about. The documentation doesn’t say anything about the double click behaviour of the console in regards to this attribute, because it has no influence on it.

So it would be nice if you could actually share what your issue is and not just necropost some generic statement and run away. Otherwise I will remove all the necroposts as they have zero value added.