Hi!
First of all, looping in @o3de/sig-ui-ux

I have an issue with this change - shapes can be used by all sorts of components, like ones related to landscape or collision.
In those cases, the collider needs to be invisible during simulation/gameplay, but being able to see it when the entity is selected in the editor allows users to clearly edit its size and proportions to fit their needs, especially through component mode. So I think this should not be changed.

What I can agree on is that the labeling / description could be improved if it caused confusion, or we could add an additional option to always hide if that fits some other workflow that is not accounted for. Feel free to elaborate the need further so we can discuss action :)

Agree, the Edit behavior needs to be changed, like when in Edit Mode it should show the shape, but here an example what I do not like. I tell the component to do this:

I de-selected the 'Visible' property but it is still visible, yes because it is selected. But my choice is ignored. Most of the time I do end up changing then the 'Filled' property. So the current behavior forces me to see this shape if I want it or not. Or, yes renaming it would be better but still, disabling completely would be nice too.
In this case I am having a 'Diffuse Probe Grid' and want to play with the parameters from this distance, but the shape is visible because I need to select the component.
Yeah I know, might be a personal preference thing :D.

Quote reply

No matter what, I recommend updating the display text to say visible in editor or editor visibility. After that you can add another flag to toggle the behavior you're describing to completely hide the shape in all cases. Even better, rename the variable and the display text to editor visibility and make it an enum with visibility modes for never, always, and when selected. Have it default to when selected. You might also need to add a serializer or something to handle the version change to preserve backward compatibility.