From 50f3a8e312d5449771ff12843471731996c0f2d6 Mon Sep 17 00:00:00 2001 From: Hugo Locurcio Date: Wed, 23 Sep 2020 23:24:58 +0200 Subject: Improve documentation related to printing error/warning messages --- modules/gdscript/doc_classes/@GDScript.xml | 2 ++ 1 file changed, 2 insertions(+) (limited to 'modules/gdscript/doc_classes/@GDScript.xml') diff --git a/modules/gdscript/doc_classes/@GDScript.xml b/modules/gdscript/doc_classes/@GDScript.xml index 918581bc9b..613039754f 100644 --- a/modules/gdscript/doc_classes/@GDScript.xml +++ b/modules/gdscript/doc_classes/@GDScript.xml @@ -818,6 +818,7 @@ a = [1, 2, 3] print("a", "b", a) # Prints ab[1, 2, 3] [/codeblock] + [b]Note:[/b] Consider using [method push_error] and [method push_warning] to print error and warning messages instead of [method print]. This distinguishes them from print messages used for debugging purposes, while also displaying a stack trace when an error or warning is printed. @@ -891,6 +892,7 @@ [codeblock] push_error("test error") # Prints "test error" to debugger and terminal as error call [/codeblock] + [b]Note:[/b] Errors printed this way will not pause project execution. To print an error message and pause project execution in debug builds, use [code]assert(false, "test error")[/code] instead. -- cgit v1.2.3