The IsThreadSafe property only tells Carmenta Engine that the custom operator implementation is thread-safe. Actually making the implementation thread-safe is the responsibility of the implementor.

Setting IsThreadSafe to false only prevents TileLayer, GlobeTileLayer, GlobeView.ElevationInput, GlobeView.SurfaceLayers and GlobeView.AuxiliaryGroundInput from invoking the same custom operator instance in parallel. If the custom operator performs non-thread-safe accesses to global variables, it is unsafe to use multiple instances of the custom operator in different layers.

The isThreadSafe property only tells Carmenta Engine that the custom operator implementation is thread-safe. Actually making the implementation thread-safe is the responsibility of the implementor.

Setting isThreadSafe to false only prevents TileLayer, GlobeTileLayer, GlobeView::elevationInput, GlobeView::surfaceLayers and GlobeView::auxiliaryGroundInput from invoking the same custom operator instance in parallel. If the custom operator performs non-thread-safe accesses to global variables, it is unsafe to use multiple instances of the custom operator in different layers.

The isThreadSafe property only tells Carmenta Engine that the custom operator implementation is thread-safe. Actually making the implementation thread-safe is the responsibility of the implementor.

Setting isThreadSafe to false only prevents TileLayer, GlobeTileLayer, GlobeView.elevationInput, GlobeView.surfaceLayers and GlobeView.auxiliaryGroundInput from invoking the same custom operator instance in parallel. If the custom operator performs non-thread-safe accesses to global variables, it is unsafe to use multiple instances of the custom operator in different layers.

The isThreadSafe property only tells Carmenta Engine that the custom operator implementation is thread-safe. Actually making the implementation thread-safe is the responsibility of the implementor.

Setting isThreadSafe to false only prevents TileLayer, GlobeTileLayer, GlobeView.elevationInput, GlobeView.surfaceLayers and GlobeView.auxiliaryGroundInput from invoking the same custom operator instance in parallel. If the custom operator performs non-thread-safe accesses to global variables, it is unsafe to use multiple instances of the custom operator in different layers.