# Enable/Disable Controls **URL:** \ **Category:** Feature Requests\ **Created:** [December 17, 2020, 8:25pm UTC](https://community.glideapps.com/t/enable-disable-controls/20007 "2020-12-17T20:25:44Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![wjcv06](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/wjcv06/32/12747_2.png) [@wjcv06](https://community.glideapps.com/u/wjcv06)\ **Post date:** [December 17, 2020, 8:25pm UTC](https://community.glideapps.com/t/enable-disable-controls/20007/1 "2020-12-17T20:25:44Z")
It would be great to add a property to enable or disable controls (checkboxes, textboxes, radio buttons, etc.) even a readonly property ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/3/0/30efa0450e4a4e1dba9253cd73558366e6ec6743.png) ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/8/688930dc8d10e45487f10fefdf03e12b6d0a07b8.png) ---
**Author:** ![Pablo\_books](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/pablo_books/32/2110_2.png) [@Pablo\_books](https://community.glideapps.com/u/Pablo_books)\ **Post date:** [December 17, 2020, 10:27pm UTC](https://community.glideapps.com/t/enable-disable-controls/20007/2 "2020-12-17T22:27:28Z")
You can make the default value checked, and then filter visibility by checkmark is _not_ checked. Which will be impossible. ---
**Author:** ![wjcv06](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/wjcv06/32/12747_2.png) [@wjcv06](https://community.glideapps.com/u/wjcv06)\ **Post date:** [December 17, 2020, 11:11pm UTC](https://community.glideapps.com/t/enable-disable-controls/20007/3 "2020-12-17T23:11:51Z")
The idea is keep always visible ---
**Author:** ![Pablo\_books](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/pablo_books/32/2110_2.png) [@Pablo\_books](https://community.glideapps.com/u/Pablo_books)\ **Post date:** [December 17, 2020, 11:19pm UTC](https://community.glideapps.com/t/enable-disable-controls/20007/4 "2020-12-17T23:19:27Z")
So you want the checkbox’s default value to be checked? There’s a default value option. I’m not very sure what your request is. ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [December 18, 2020, 12:05am UTC](https://community.glideapps.com/t/enable-disable-controls/20007/5 "2020-12-18T00:05:36Z")
It’s just for the ability to disable and prevent the user from changing the value in an entry component, but still keep it visible. This is common in many development environments where you can set ‘object.enabled’ to true or false on an object (component). It can signify that something is available, but currently not allowed to be changed either due to it not applying to a current situation, or maybe someone not having authority to make a change. Think about the case of a detail screen with entry components and with a filter on the screen that prevents it from attaching to an existing row. All entry components become greyed out and disabled so you can’t edit them, but they are still visible. Another case is a form that has a submit button greyed out due to not having all required fields filled in. Those are most likely coded with a .enabled=false. ---
**Author:** ![wjcv06](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/wjcv06/32/12747_2.png) [@wjcv06](https://community.glideapps.com/u/wjcv06)\ **Post date:** [December 18, 2020, 12:18am UTC](https://community.glideapps.com/t/enable-disable-controls/20007/6 "2020-12-18T00:18:51Z")
Exactly, all programming languages have it ---
**Author:** ![Pablo\_books](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/pablo_books/32/2110_2.png) [@Pablo\_books](https://community.glideapps.com/u/Pablo_books)\ **Post date:** [December 18, 2020, 12:40am UTC](https://community.glideapps.com/t/enable-disable-controls/20007/7 "2020-12-18T00:40:18Z")
Ah, I see. That’s a good idea. Perhaps there should be an option on entry components for allow entry if {condition} else, display entry ---
**Author:** ![wjcv06](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/wjcv06/32/12747_2.png) [@wjcv06](https://community.glideapps.com/u/wjcv06)\ **Post date:** [December 18, 2020, 12:45am UTC](https://community.glideapps.com/t/enable-disable-controls/20007/8 "2020-12-18T00:45:12Z")
enabling should be exactly equal to visibility ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [December 18, 2020, 7:25am UTC](https://community.glideapps.com/t/enable-disable-controls/20007/9 "2020-12-18T07:25:12Z")
> [@Jeff\_Hager](#): > > Think about the case of a detail screen with entry components and with a filter on the screen that prevents it from attaching to an existing row. All entry components become greyed out and disabled so you can’t edit them, but they are still visible. A workaround to this that I have been using is to simply use a text component to display the actual value if the item isn’t editable in the current context.