# Closing Vision Window instance on separate clients

**URL:** <https://forum.inductiveautomation.com/t/closing-vision-window-instance-on-separate-clients/96905>\
**Category:** Ignition\
**Tags:** ignition81, vision, scripting\
**Created:** [October 7, 2024, 2:17pm UTC](https://forum.inductiveautomation.com/t/closing-vision-window-instance-on-separate-clients/96905 "2024-10-07T14:17:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [October 7, 2024, 2:42pm UTC](https://forum.inductiveautomation.com/t/closing-vision-window-instance-on-separate-clients/96905/2 "2024-10-07T14:42:42Z")

</div>

This is extremely difficult and fragile, as described. Instead, consider allowing the window to always be opened, but all of its features **disabled** by default.

Then, set up a couple memory tags. One to hold the client ID of the client "in control", and a second to contain a datetime **timeout** value.

Enable the controls on the window while the particular client's ID matches and the timeout timestamp is greater than `now()`.

Use a button on the window to "claim" control by writing the current client ID to the memory tag, with a timeout a short time in the future.

(The claim button would also be disabled when some other client has control.)

---

_[View the full topic](https://forum.inductiveautomation.com/t/closing-vision-window-instance-on-separate-clients/96905)._