Bug? Duplicated components don't share component color

[GRSnyder]

If it's a bug it's just a nit, albeit a somewhat confusing one. It relates to the "component colors" pseudo-color modeling view.

According to the browser, duplicated components share the same component color. If you pick Cycle Component Color on either component in a duplicate pair, the color swatch for the other also updates. However, the actual 3D view updates the color for only the selected component.

I'm not arguing that either convention (duplicates share a component color, or they don't) is necessarily better. My beef is that the display is inconsistent. Actual component colors should always match the swatch displayed next to their names in the browser.

[Phil.E]

I can't reproduce that effect. Can you share the design?

[GRSnyder]

---

@Phil.E wrote: I can't reproduce that effect. Can you share the design?

---

Sure, although it probably won't help: saving the design and reopening it synchronizes the colors. However, after reopening, the desynchronizing effect is still 100% reproducible with a second color cycle.

I suspect that this is a recent regression - I think I would have noticed it before otherwise, since I usually work in component color mode and do use duplicated components pretty often. Also, I'm using a Mac. A screencast of the effect is attached as well.

Screencast link: https://autode.sk/33MiAnX

[Phil.E · Accepted solution]

Thanks I got it now. Forgot all about the cycle component color command.

What's happening is the color is getting cycled for the one instance and not the other, in canvas. The browser picks up the change. If you compute all at this point it will make browser and canvas objects all the right color.

Thanks again for the report.