From 634d057a52f87e33c9a7b799aa8fcf661901d9de Mon Sep 17 00:00:00 2001 From: Fabio Alessandrelli Date: Tue, 11 Sep 2018 18:36:43 +0200 Subject: Less verbose ScriptDebugger, message on connect. Short diff, long explaination: This will hopefully clarify whether or not issues are about the dubgger like the case of the never ending thread about MacOS "Remote debugger fails", which started as a real issue, and ended up being referenced for every strange OSX issue where the window was not visible or the engine crashed without appearing on screen. --- core/script_debugger_remote.cpp | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'core') diff --git a/core/script_debugger_remote.cpp b/core/script_debugger_remote.cpp index 0519807e63..704b4d1fdc 100644 --- a/core/script_debugger_remote.cpp +++ b/core/script_debugger_remote.cpp @@ -77,18 +77,19 @@ Error ScriptDebuggerRemote::connect_to_host(const String &p_host, uint16_t p_por for (int i = 0; i < tries; i++) { if (tcp_client->get_status() == StreamPeerTCP::STATUS_CONNECTED) { + print_verbose("Remote Debugger: Connected!"); break; } else { const int ms = waits[i]; OS::get_singleton()->delay_usec(ms * 1000); - ERR_PRINTS("Remote Debugger: Connection failed with status: '" + String::num(tcp_client->get_status()) + "', retrying in " + String::num(ms) + " msec."); + print_verbose("Remote Debugger: Connection failed with status: '" + String::num(tcp_client->get_status()) + "', retrying in " + String::num(ms) + " msec."); }; }; if (tcp_client->get_status() != StreamPeerTCP::STATUS_CONNECTED) { - ERR_PRINTS("Remote Debugger: Unable to connect."); + ERR_PRINTS("Remote Debugger: Unable to connect. Status: " + String::num(tcp_client->get_status())); return FAILED; }; -- cgit v1.2.3