Effect of Minimum Timer Debug output control

Post Reply
User avatar
SlySven
Posts: 919
Joined: Mon Mar 04, 2013 3:40 pm
Location: Deepest Wiltshire, UK
Discord: SlySven#2703

Effect of Minimum Timer Debug output control

Post by SlySven » Fri Oct 14, 2016 1:51 am

Recently introduce to the codebase was a control to reduce the possibly spammy output for Timers in the Debug console window.

Suppose there is a Timer with more than a few lines of "script" that fires every second like in the follow example; by default, every time it fire the entire contents of the script (or a command if that is set) is echoed to the Debug Console - and it can quickly fill up the window:
Mudlet_timer_spam_before.png
Now, by setting a control on the Special Options tab on the Profile Preferences, you can have the output of timers with a duration less than the given duration NOT output all the detail:
Mudlet_timer_debug_spam_limit_default.png
Mudlet_timer_debug_spam_limit_default.png (42.57 KiB) Viewed 2348 times
Note that you can remove the detail (but NOT the line that says which timer was run) - this is the same output for the same duration:
Mudlet_timer_spam_after.png
Mudlet_timer_spam_after.png (6.67 KiB) Viewed 2348 times
To restore the display of everything (as before) you can wind the control back down to a zero time (in hours:minutes:seconds.milliseconds, as per the timer duration setting controls) - where it will display "show all":
Mudlet_timer_debug_spam_limit_asBefore.png
Mudlet_timer_debug_spam_limit_asBefore.png (30.88 KiB) Viewed 2348 times

Post Reply

Who is online

Users browsing this forum: No registered users and 6 guests