FreeCADHello, everyone, I just started exploring Part Design, so the question may be dumb. Please bear with me.
Say, I have a screw object, and want 100 instances to put in various places, how can this be achieved using the new App::Part? Using ShapeBinder? From its code I can see that it does simply return the shape from its linked object if no sub element is involved, but it has its own ViewProvider, which means, a change in the base object will trigger an update of all ViewProvider instances. That's obviously not a desired behavior, right? Why can't we just reuse the very same ViewProvider of the object, and simply add a SoTransform node for each instance, and be done with it? And I think Coin3D supports that, right, I mean inserting a node into multiple parents? So, if we put this node sharing thing inside ViewProviderPart, I don't see why can't an object be inside multiple App::Part.
In fact, I can't seem to find any use case of node sharing in FC. Maybe someone tried it and it didn't work? Imaging what if it works, what are the possibilities! Say, let an object appear in multiple documents multiple times with minimum overhead, and I am talking about assemblies, of course. Anyone?
.
