# Objects Visible Property in Development Enviroment

**URL:** <https://forum.inductiveautomation.com/t/objects-visible-property-in-development-enviroment/15455>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [September 24, 2017, 1:44am UTC](https://forum.inductiveautomation.com/t/objects-visible-property-in-development-enviroment/15455 "2017-09-24T01:44:11Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sfitze](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@sfitze](https://forum.inductiveautomation.com/u/sfitze)\
**Post date:** [September 27, 2017, 6:14pm UTC](https://forum.inductiveautomation.com/t/objects-visible-property-in-development-enviroment/15455/3 "2017-09-27T18:14:33Z")

</div>

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)
&& // and (logical and)
!({[System]Client/System/SystemFlags} & 2) // not testing (bitwise and with next to lowest bit)
|| // or (logical or)
{your/tag/that/controls/visiblity} // your condition(s) ...
```

---

_[View the full topic](https://forum.inductiveautomation.com/t/objects-visible-property-in-development-enviroment/15455)._