# Object visibility in Vision Designer

**URL:** <https://forum.inductiveautomation.com/t/object-visibility-in-vision-designer/72155>\
**Category:** Ignition Exchange\
**Tags:** vision, ignition81\
**Created:** [April 6, 2023, 3:31pm UTC](https://forum.inductiveautomation.com/t/object-visibility-in-vision-designer/72155 "2023-04-06T15:31:10Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [April 8, 2023, 5:22pm UTC](https://forum.inductiveautomation.com/t/object-visibility-in-vision-designer/72155/10 "2023-04-08T17:22:35Z")

</div>

You can get the functionality you want by adding conditions for in designer and not testing to your visibility expression in addition to your usual visibility expressions:

> [@Design Mode defualt View irrespactive of bindings for Customised templates/componenets](https://forum.inductiveautomation.com/t/design-mode-defualt-view-irrespactive-of-bindings-for-customised-templates-componenets/36745/6):
>
> If you use expression bindings, you can add this condition to display as desired when in Designer and not testing–a “design mode”: // Show this if in designer and not testing. (({[System]Client/System/SystemFlags} & 1) && !({[System]Client/System/SystemFlags} & 2)) // Also show under these conditions in client or testing in designer. || runtimeCondition Replace runtimeCondition with the expression you’d want evaluated for the binding in a client.

---

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