To make your networks portable, whats a better option than relying on parent(). references in nested compositions?
What’s wrong with parent()?
Parent Shortcuts are a feature beyond that if you want something that is more move-able within the parent network though.
One option is to RMB->CreateInternalParameters, which adds a Base COMP into your current network. You then add custom parameters onto that Base COMP to control your network (by referencing iparLocal.par.. This is a solid way to have good local control
However, IMO the trick to making things really portable is to treat each COMPonent as a black box, i.e. you pass in some data via custom parameters, and then get the results out either visually or via Out DAT/CHOPs. Thus the outside doesn’t know how the inside works, and the inside doesn’t refer to anything beyond its enclosing container.