Setting up a system of Dynamic Components

[mathieubrassard1987]

Im not the original poster but my dynamic components are become very heavy and are crumbling under their own weights. Much of what you said seems helpful but I dont understand how to apply it.

@pcmoor

Use the instance name for identification, do not use the name attribute in the DC, this will assure uniformity in the model outliner and label, plus the DC label.

From what I understand there are four places where there can be a name for the component.

• Instance
• Definition
• Component info > name
• Dynamic component > Object name (double click top left)

From my experience, there is only the “Object name under dynamic component” that you can reference. The “Component info > name” is only displayed in the component options, no? Its only for the user or the reports? Its purely aesthetical , isnt it?

@pcmoor

Have a system of simplification of the DC. It reduces the file size, protects the result from change or intellectual loss. This is required for label of a parent otherwise the label reports the sub components. The actions once sorted can be done with a script.

How? Can you elaborate on it? Provide a simple example?

@pcmoor

Use a standard attribute for layout text, then no need to search for data for each component

Once again, what do you mean? At what point? Are you talking about “component info > description”?

That being said I really could use some help with my crumbling under its own weight dynamic components. If you were up for a hangout or something along those lines that would be great!

Thanks for the clarification!