# Visibility in the designer

**URL:** <https://forum.inductiveautomation.com/t/visibility-in-the-designer/25555>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [June 4, 2019, 8:55pm UTC](https://forum.inductiveautomation.com/t/visibility-in-the-designer/25555 "2019-06-04T20:55:44Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\
**Post date:** [June 5, 2019, 6:36am UTC](https://forum.inductiveautomation.com/t/visibility-in-the-designer/25555/4 "2019-06-05T06:36:08Z")

</div>

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

> [@Objects Visible Property in Development Enviroment](http://forum.inductiveautomation.com/t/objects-visible-property-in-development-enviroment/15455/3):
>
> 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…

---

_[View the full topic](https://forum.inductiveautomation.com/t/visibility-in-the-designer/25555)._