From 47c615caf3701c25743d0b7aa68cde49958ca09c Mon Sep 17 00:00:00 2001 From: Hugo Locurcio Date: Wed, 31 Jul 2019 17:24:53 +0200 Subject: Cap the number of warnings/errors per second rather than per frame This reproduces the behavior used for printing when using the remote debugger. The default limit is 100 errors and 100 warnings per second, which makes it possible to display much more GDScript warnings before overflowing. This also adds a "Too many warnings" message, so that warnings don't look like errors when overflowing anymore. This closes #21896. --- core/script_debugger_remote.h | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'core/script_debugger_remote.h') diff --git a/core/script_debugger_remote.h b/core/script_debugger_remote.h index 1fc9d7c7f1..a5bfd7a32d 100644 --- a/core/script_debugger_remote.h +++ b/core/script_debugger_remote.h @@ -91,11 +91,15 @@ class ScriptDebuggerRemote : public ScriptDebugger { int max_messages_per_frame; int n_messages_dropped; List errors; - int max_errors_per_frame; + int max_errors_per_second; + int max_warnings_per_second; int n_errors_dropped; + int n_warnings_dropped; int max_cps; int char_count; + int err_count; + int warn_count; uint64_t last_msec; uint64_t msec_count; -- cgit v1.2.3