# Bi-Directional Bindings vs writeBlocking **URL:** \ **Category:** Ignition\ **Created:** [September 4, 2024, 1:16pm UTC](https://forum.inductiveautomation.com/t/bi-directional-bindings-vs-writeblocking/95526 "2024-09-04T13:16:21Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [September 4, 2024, 5:28pm UTC](https://forum.inductiveautomation.com/t/bi-directional-bindings-vs-writeblocking/95526/6 "2024-09-04T17:28:16Z")
Prior discussion over here: > [@Ignition Edge Vision Client Screen Lock](https://forum.inductiveautomation.com/t/ignition-edge-vision-client-screen-lock/95368): > > Can anyone tell me where to look for a problem when a vision client screen gets locked up? We have Panel PCs with Ignition Edge Panel. When a user touches a button that writes to tags (using bi-directional custom properties, not the writeBlocking script) the screen locks up and they cannot touch anything else on the screen. I say touch because I was remoted in via VNC and could click around when the local user could not. Anyone have any ideas on what could be locking up the screen? Jacob, see the "Keep it tidy" section of [this forum's rules](https://forum.inductiveautomation.com/faq). --- _[View the full topic](https://forum.inductiveautomation.com/t/bi-directional-bindings-vs-writeblocking/95526)._