Hi Johnson, thanks for the detailed reply. This definitely does seem convoluted. But I'm trying to see if we can make it work as it is now.
But after some testing, I'm finding undependable results, even using a non-master View Rep. This was my workflow:
- Edit Derive feature in Cube.ipt and Cylinder.ipt to use "Front" view rep of Multibody.ipt (associative NOT checked, because that would force all solids to derive in). After changing to "Front", turn off the inclusion of the opposite solid that got turned on when "Front" was chosen (e.g., for Cube.ipt, turn off the inclusion of the "Cylinder" solid body).
- Open Multibody.ipt and activate the "Front" view rep
- Change appearance of Cube and/or Cylinder solid within Multibody.ipt with "Front" view rep active
- Open Multibody.iam
But even with using the non-Master "Front" view rep, the "Update" icon does not activate, and the appearances have not updated correctly. Even if I specifically open Cube.ipt and Cylinder.ipt, they do not update, and the Update button is not active. For me, the behavior is the same as before. Even with "Front" being used for the Derive, I still have to edit the Derive and "OK" with no changes to get the appearance change to carry over.
So, just for testing purposes, I tried to check on "Associative" for the Derive feature. This was my workflow:
- Within Multibody.iam, turn off the visibility of Cylinder:1 altogether (in preparation for the fact that we're about to display both solids within Cube.ipt).
- Open Cube.ipt, and edit the Derive feature.
- Check "Associative" to ON for the Front view rep. Commit the change. Both solids should now be displayed in Cube.ipt.
- Open Multibody.ipt and change the appearance of both solids.
- Open Multibody.iam.
But even after checking "Associative" on, the appearances do not update and the "Update" icon is not active! Only if I explicitly open "Cube.ipt" does the "Update" button finally activate. After clicking it, the color finally updates correctly. But this is hardly better than before. It's not feasible for me to have to guess which parts need to be updated, open each one individually, and update it. Plus this isn't a realistic workflow anyway, because we can't realistically keep up with one view rep within Multibody.ipt for every solid it has (some of our multibodies have dozens of solids). So checking associative isn't a viable option, anyway.
Am I doing something wrong, or can you reproduce these inconsistencies as well?