That workaround wouldn’t work for us, since the RepeatGrid
pluginData would have to point to arbitrary subnodes, and we can’t store scenenode pointers. And, also, when you’re adding/deleting metadata from subnodes in the proper edit context, we couldn’t modify the
pluginData of the RepeatGrid node itself. So there’s no way to keep both “sides” (top level and interior nodes) in synch.
Here’s the usage context which might help motivate what I’m asking for.
If I have some metadata on a repeat grid sub-node, I can refresh the whole grid by walking all subnodes of the grid’s first child, and using the
attach...Series API. But if I want to clear all that metadata from top-level, I can’t, because I can’t descend into the grid and clear individual nodes’
So there’s not as clean a UX, where I can refresh the whole grid but can’t clear it from the top-level.