Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X
In the default combined state of my part, I don't want the annotations to be present. For those that come from a skeleton model, I can unassign them and they go away from the display.
Problem is, upon regeneration, they come back as the systems re-assigns them to the combined active state.
I notice this auto-reassignment can be stopped by placing the source skeleton model into a state where the annotations are not shown. I don't always remember to do this, so it becomes a bit of a pain in the neck to manage the display of annotations in my models.
I wonder if there is a config.pro setting that prevents this auto-addition of annotations.
Solved! Go to Solution.
Ok, I think I finally see. The published annotations from the skeleton model that are on its "Default All" combined state will re-appear in the target model's "Default All" combined state when it is regenerated.
So solution is to remove these annotations from the skeleton model's "Default All" state.
Ok, I think I finally see. The published annotations from the skeleton model that are on its "Default All" combined state will re-appear in the target model's "Default All" combined state when it is regenerated.
So solution is to remove these annotations from the skeleton model's "Default All" state.