Thomas Sarkanen 80872dc886 Improved and added optional limits around private members to Blueprint thread safety checks ...

Currently it is not 'safe' for external code/scripts to be able to 'poke' data that is ostensibly thread-safe. Restricting to only private data is one possible option to solve this.
Gated behind a config flag for now as most content does not obey these rules at the moment.

This change also covers a case with 'valid' UObject use on worker threads where those UObjects are returned from thread-safe functions (which can only be native given the BP-level checks). It is assumed that the native thread-safe fucntion returning a UObject 'knows' that the UObject should be safe to access (e.g. some sub-object like a linked anim instance).

#rb Phillip.Kavan

[CL 16569224 by Thomas Sarkanen in ue5-main branch]

2021-06-07 08:45:27 -04:00

..

Private

Improved and added optional limits around private members to Blueprint thread safety checks

2021-06-07 08:45:27 -04:00

Public

Added the concept of thread safe Blueprint functions

2021-05-19 04:47:35 -04:00

KismetCompiler.Build.cs

Adding EditorFramework to build.cs files

2020-08-14 13:24:16 -04:00