Hmm, okay, here's a way to roughly do what you're asking:
1. Make a new customparamset while your parent is branch-selected. Give it whatever boolean params you need. 2. Set the param values via ICE with a simple SetData (self.MyProperty.MyParam), on your parent's icetree. 3. On the children, set an expression on your viewvis or whatever parameter. Something like: this.MyParamSet.MyParam Because of branch-propagation of the parent property, your paramset will appear to live on your children, so using "this" is valid. 4. Feel free to rightclick and Copy/Paste Animation to set the expression accordingly on all the other children objects. They should now be getting the ICE-driven values propagated correctly. Is that more or less what you wanted? On Thu, Jun 20, 2013 at 9:58 AM, Ponthieux, Joseph G. (LARC-E1A)[LITES] < [email protected]> wrote: > I could yes. It’s an older asset and isn’t set up that way, but frankly > that makes a lot of sense.**** > > ** ** > > ** ** > > ** ** > > Admittedly what I was really hoping for, was that there was an ICE > solution,. So for example instead of using:**** > > ** ** > > “self.visibility.viewvis”**** > > ** ** > > I could something like:**** > > ** ** > > “all.visibility.viewvis”**** > > ** ** > > or:**** > > ** ** > > “branch.visibility.viewvis”**** > > ** ** > > or:**** > > ** ** > > “model.visibility.viewvis”**** > > ** ** > > And the visibility parameter would just propagate through the selected > object and down the hierarchy. Since it already is able to assume the > selected object without a name, why shouldn’t it be able to assume the > selected object’s hierarchy without a name?**** > > ** ** > > ** ** > > --**** > > Joey Ponthieux**** > > LaRC Information Technology Enhanced Services (LITES)**** > > Mymic Technical Services**** > > NASA Langley Research Center**** > > __________________________________________________**** > > Opinions stated here-in are strictly those of the author and do not **** > > represent the opinions of NASA or any other party.**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Alan Fregtman > *Sent:* Wednesday, June 19, 2013 7:00 PM > *To:* XSI Mailing List > *Subject:* Re: Can you see me now?**** > > ** ** > > Is there any reason you can't go with a good ol' drag&drop expression?**** > > ** ** > > If you need to copy the same expression on many objects, once you have one > just rightclick and Copy/Paste Animation, unless I'm missing something > obvious here.**** > > ** ** > > ** ** > > On Wed, Jun 19, 2013 at 3:32 PM, Ponthieux, Joseph G. (LARC-E1A)[LITES] < > [email protected]> wrote:**** > > I’ve got a model hierarchy of dozens of parts under a parent object.**** > > **** > > The parent object is animated via an ICE tree and I’ve added conditional > behavior to the ice tree to affect things like visibility of the parent > object when certain situations are met.**** > > **** > > This is all working as I would like with one except. I’d like the > visibility condition to propagate from the parent to the entire model.**** > > **** > > Am I required to apply a setdata node of visibility for every child of the > parent, or is there an easier way?**** > > **** > > I seem to recall I would have performed a branch key in the past, but I > have no clue how this might translate to ICE.**** > > **** > > --**** > > Joey Ponthieux**** > > LaRC Information Technology Enhanced Services (LITES)**** > > Mymic Technical Services**** > > NASA Langley Research Center**** > > __________________________________________________**** > > Opinions stated here-in are strictly those of the author and do not **** > > represent the opinions of NASA or any other party.**** > > **** > > ** ** >
