From be0733a5b51be436a8fdd285da025a5ce18f6733 Mon Sep 17 00:00:00 2001 From: Mason Bially Date: Mon, 4 May 2020 10:04:21 -0700 Subject: [PATCH] Attempting to clean up thread safe language. (#3336) * Attempting to clean up thread safe language to remove confusing and conflicting repetition. * Update tutorials/threads/thread_safe_apis.rst Co-authored-by: Max Hilbrunner --- tutorials/threads/thread_safe_apis.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorials/threads/thread_safe_apis.rst b/tutorials/threads/thread_safe_apis.rst index 99572e007..218790e6b 100644 --- a/tutorials/threads/thread_safe_apis.rst +++ b/tutorials/threads/thread_safe_apis.rst @@ -57,4 +57,4 @@ In GDScript, reading and writing elements from multiple threads is ok, but anyth Resources --------- -Modifying a unique resource from multiple threads is not supported, but loading them on threads or handling a reference is perfectly supported. Scenes, textures, meshes, etc. Can be loaded and manipulated on threads, then added to the active scene in the main thread. +Modifying a unique resource from multiple threads is not supported. However handling references on multiple threads is supported, hence loading resources on a thread is as well - scenes, textures, meshes, etc - can be loaded and manipulated on a thread and then added to the active scene on the main thread. The limitation here is as described above, one must be careful not to load the same resource from multiple threads at once, therefore it is easiest to use **one** thread for loading and modifying resources, and then the main thread for adding them.