You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To improve the UX of the Dalamud Console (Log), I would like to request a feature that consolidates repeating messages, similar to how the javascript console works in your browser.
This way, when an exception occurs, or printing log lines during a UiBuilder.Draw or Framework.Update callback, your console window would not be spammed full with the same lines over and over again. This would also make debugging issues easier in case some log message before an exception would help indicate where a potential problem lies.
As for behavior of when to consolidate messages, I'd advocate to keep it simple and predictable: Only check for the last line in the window and compare that with an incoming message. If the message (and plugin source) is the same, simply update the timestamp of the last line (or just replace it, whatever implementation is easier). As a bonus, add a message counter somewhere to let the user know that the message has occurred multiple times.
The text was updated successfully, but these errors were encountered:
To improve the UX of the Dalamud Console (Log), I would like to request a feature that consolidates repeating messages, similar to how the javascript console works in your browser.
This way, when an exception occurs, or printing log lines during a
UiBuilder.Draw
orFramework.Update
callback, your console window would not be spammed full with the same lines over and over again. This would also make debugging issues easier in case some log message before an exception would help indicate where a potential problem lies.As for behavior of when to consolidate messages, I'd advocate to keep it simple and predictable: Only check for the last line in the window and compare that with an incoming message. If the message (and plugin source) is the same, simply update the timestamp of the last line (or just replace it, whatever implementation is easier). As a bonus, add a message counter somewhere to let the user know that the message has occurred multiple times.
The text was updated successfully, but these errors were encountered: