Suppose you have ViewX and ViewY. ViewX contains an Embedded View, and that Embedded View supplies the path to ViewY, such that you can see ViewY rendered within ViewX.
The only properties you have access to are those which you see in the property editor, so no, you are not able to reference children of ViewY from any scripting in ViewX.
If you need to communicate with children of ViewY from within ViewX, there are three ways to do so. I’ll provide them in order of how much they make sense.
- params: if you need to tell ViewY about something - and potentially get information back - params are a fairly easy way to do so. I recommend using in/out params for most scenarios.
- Message Handling: While this requires setting up a whole message send/receive paradigm for the components in question, it is far more recyclable and prevents you the need to link bindings to the params.
- Bind values to custom session properties. This route works, but requires you to manage a growing list of properties at the session scale. Negligible performance degradation, but I have one project which has hundreds of properties, sometimes nested deep within objects. Whenever I need to reference such a property, I know it’ll be at least a few minutes before I can locate it.