bug in component color cycling

[robduarte]

Hi all,

Please see this video for an explaination. There is an inconsistency when coloring components that have been created using "Convert bodies to components".

http://www.youtube.com/watch?v=BCJ3y3om2AE

[jeff_strater]

Hi @robduarte.  You are right, this is a little confusing.  Technically the color cycling shows which component owns the feature.  So, a New Component feature is actually owned by the parent component, for instance.  You can see this if you create a new component, then do a Box feature.  Only the Box feature is colored to match the component, and only the Box shows up if you activate this component.  However, Create Component From Body is a bit different.  It does two things.  It creates a component, and moves the body into that component.  If it were split into two features, there would be a Create Component feature owned by the parent, and a CutPasteBody feature owned by the new component, and colored the same.  However, for simplicity, we grouped them together.  So, the Create Component From Body feature is owned by the parent (indicating its color), but we also show it when the component is active, because otherwise, the timeline would be empty.

Hope this helps your understanding a little bit.

Jeff Strater (Fusion development)

[robduarte]

Thanks for the reply. I think I see what you mean. If I make changes to that component (add another body and combine it with the existing one for example) I do see the correct color reflected in the design history for subsequent features. Still confusing, though, since I'd expect all component colors to work the same no matter how the component was initially created.