Programmatically and theoretically, this is correct, but this is what I’m exploring - essentially, what needs to be tested is the performance across receiving connectors:
-
In some instances (no pun intended), I anticipate SpeckleToNative to create new objects in a new location, and then the parent transform will not be present on resend but the transform has been “baked”.
-
In some other instances, the parent transform may be interpreted as a collection as any other and persist in republishing.
-
In others, this operation is not anticipated, in which case behaviour and outcome are unknown.
In essence, this is my exploration with a view to see what support we can offer for the use case reported by @Jonathan_Rabagliati : Moving ALL Geometry in an entire Speckle Stream/Project - #5 by Jonathan_Rabagliati