# Gui bug - I can still us gui.pick\_node() on a node which is disabled

**URL:** <https://forum.defold.com/t/gui-bug-i-can-still-us-gui-pick-node-on-a-node-which-is-disabled/75976>\
**Category:** Bugs\
**Created:** [February 12, 2024, 3:35am UTC](https://forum.defold.com/t/gui-bug-i-can-still-us-gui-pick-node-on-a-node-which-is-disabled/75976 "2024-02-12T03:35:58Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![einar](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/einar/32/31951_2.png) [@einar](https://forum.defold.com/u/einar)\
**Post date:** [February 12, 2024, 10:49am UTC](https://forum.defold.com/t/gui-bug-i-can-still-us-gui-pick-node-on-a-node-which-is-disabled/75976/4 "2024-02-12T10:49:10Z")

</div>

Isn’t it like that by design? I found this old thread [Gui.set\_enabled doesn’t prevent gui.pick\_node in Input](https://forum.defold.com/t/gui-set-enabled-doesnt-prevent-gui-pick-node-in-input/28819). EDIT: maybe the intended behavior was changed since then.

---

_[View the full topic](https://forum.defold.com/t/gui-bug-i-can-still-us-gui-pick-node-on-a-node-which-is-disabled/75976)._