does the data need to persist in the scene? if so, use the datablobs
otherwise there is Plugin.UserData very much like data blobs but
doesn't persist or have a property in the scene. i use them in my tape
measure plugin to persist the history of measurements taken between
uses. that code is available on my github page.
*written with my thumbs
On May 7, 2013, at 5:43 AM, Leonard Koch <[email protected]>
wrote:
Hi Guys,
I have a bit of a dev question here.
When I have a large datastructure which is created by one plugin,
what are the most efficient ways of making that data available to
other plugins?
To be specific I have a datastructure in memory that is written to
from the toolcontext api, written to from custom operators and read
by a set of ice nodes.
I've registered functions which give access to it, but it isn't
always very efficient so I'm asking you guys for your workflows in
matters like this.
Thanks
