# Gui.set\_enabled doesn't prevent gui.pick\_node in Input

**URL:** <https://forum.defold.com/t/gui-set-enabled-doesnt-prevent-gui-pick-node-in-input/28819>\
**Category:** Questions\
**Created:** [September 6, 2018, 7:39pm UTC](https://forum.defold.com/t/gui-set-enabled-doesnt-prevent-gui-pick-node-in-input/28819 "2018-09-06T19:39:57Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Mitch](https://forum-defold.b-cdn.net/letter_avatar_proxy/v4/letter/m/dec6dc/32.png) [@Mitch](https://forum.defold.com/u/Mitch)\
**Post date:** [April 23, 2019, 6:14pm UTC](https://forum.defold.com/t/gui-set-enabled-doesnt-prevent-gui-pick-node-in-input/28819/5 "2019-04-23T18:14:47Z")

</div>

> [@britzl](#):
>
> It’s by design, but I can agree that it might be confusing before you know that is how it works. For nested view hierarchies it’s worth pointing out that you may wish to check if a parent is disabled as well:

I ran into the same frustrating problem causing bugs with disabled GUI’s because I assumed disabling them would mean they are not pickable because they’re disabled. Easily solved by adding “gui.is\_enabled(node)” now that I found this thread. Might be worth adding to the documentation under either is\_enabled or set\_enabled to make it clearer disabled nodes are still pickable.

> gui.is\_enabled
> 
> Returns `true` if a node is enabled and `false` if it’s not. Disabled nodes are not rendered and animations acting on them are not evaluated.

> gui.pick\_node - determines if the node is pickable by the supplied coordinates

Disabled nodes are not rendered, ignore animations but are still pickable?

---

_[View the full topic](https://forum.defold.com/t/gui-set-enabled-doesnt-prevent-gui-pick-node-in-input/28819)._