-
Workflow advice request: Essential Properties in Essential Graphics prohibited
Hello all, and thanks for letting me join.
This might sound a bit dumb as a first time inquiry, but I would really like to know how people handle the problem of Essential Properties of a nested comp (L1) being excluded from the Essential Graphics Panel of the comp (L2) where said first comp L1 is nested in.
Background is that I am designing prototypes of objects, that are variable in certain aspects (hence the Essential Properties path), but will be combined to a hierarchically higher object, that is yet again a prototype for another larger structure.
In this scenario, at least IMHO, it would be practical to push through the Essential Properties of the base levels to the highest level (L3…). The workaround is to create new controls on comp L2, hook the essential properties of the L1 objects to these, and create new entries in the Essential Graphics Panel of L2 from such controls to finally give them over to L3, where L2 objects are nested.
Even though this seems to be structurally sound, it feels somehow wrong. And is cumbersome.
The bigger plan behind this BTW is to script a builder that draws together some CSV data in order to modify and place instances of L1 or L2 objects to the final L3 structure.
Am I missing something (Google Foo says no), do I want to much, or am I just being a fool?