jharp
September 10th, 2021, 21:34
I have no reason to think this is a new but (maybe it is, no idea) but I had reason to use windowinstance.close(true) to force windows to close on a client but they never do.
Maybe I'm using it for the wrong purpose but what I wanted was:
Host sets image to public. Host opens the image. Client opens the image. Host hits a new button to close it on the host side with the version closing on the client as well. Should this not work with windowinstance.close(true)?
From the API guide:
close
function close([closeclients])
Closes the window.
Parameters
closeclients (boolean) [optional]
If true and running as the host, the corresponding window will be closed for all clients that have it open as well.
For various reasons I don't want to make the image private to force the close.
Am I wrong somehow or is this a bug. I'm using 2E ruleset but I don't think this is a 2E issue.
Thanks,
Jason
Maybe I'm using it for the wrong purpose but what I wanted was:
Host sets image to public. Host opens the image. Client opens the image. Host hits a new button to close it on the host side with the version closing on the client as well. Should this not work with windowinstance.close(true)?
From the API guide:
close
function close([closeclients])
Closes the window.
Parameters
closeclients (boolean) [optional]
If true and running as the host, the corresponding window will be closed for all clients that have it open as well.
For various reasons I don't want to make the image private to force the close.
Am I wrong somehow or is this a bug. I'm using 2E ruleset but I don't think this is a 2E issue.
Thanks,
Jason