Visibility in the designer

[christopher.knapp]

Is there a way to force a component to be visible in the designer, but have a binding drive the visibility on the client?

I have certain components that I want turned on/off based on machine options, but when that option isn’t present the component is invisible in the designer as well. I’m afraid that as time goes on, someone won’t realize the work for that option is already done since they cannot see if in the designer.

I know that I can click the checkbox next to the visibility to temporarily force it on, but as soon as it transitions to “false” from the PLC tag driving that binding, it doesn’t show up again.

[brandon1]

Check this out:

Objects Visible Property in Development Enviroment

WHILE IN A LIVE SYSTEM, I’m missing how to maintain the objects visibility when in the development Enviroment, when the TAGs bound visibility is only desired to disappear in the client runtime view? Other HMI design packages include a “toggle states” menu button or when in the development mode, don’t turn off the objects visibility? The invisible objects become lost unless you know where to select the hidden object…

[cmallonee]

If you’re in Perspective, configure an Expression binding for Component.meta.visible a la

{[tag_provider_name]PathToPLC/relevantValue} || ({session.props.device.type}='designer')

I don’t know if Vision has an equivalent means…

[witman]

Vision equivalent isn't quite as clean, but does the trick (from thread linked by @brandon1 above):

Objects Visible Property in Development Enviroment

There is a system tag that holds a bit array of SystemFlags. The lowest order bit is on if you are in the designer and the next bit is on if you are testing in the designer. I usually use an expression like this in the visibility property of a component. It is visible in the designer when not testing but uses the other condition when testing or at runtime. ({[System]Client/System/SystemFlags} & 1 ) // in designer (bitwise and with lowest bit) && // a…