You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VNCScreen screen = VNCScreen.start("<ip>", 5900, "<password>", 3, 0);
for (int i = 0; i < 10; i++) {
Thread.sleep(3000);
screen.capture().save("<path>");
}
screen.stop();
When I check the saved screenshots, I notice that the images show no changes despite switching screens during the test, which should reflect the current time.
I'm puzzled by this. I'm using Windows 11 as the client with SikuliX version 2.0.5 and Java version 17. The server is Fedora 22 with tigervnc-server version 1.6.0, and on the local machine (also Windows 11) with tigervnc-server version 1.13.1. Despite trying various configuration changes during testing, I haven't seen any differences in the results.
I also tried using the screen.getClient().refreshFramebuffer(); method, but it didn't have any effect either.
Furthermore, in my script, if I don't use the screen.stop() operation, the script does not naturally stop, and there are no error messages. Even if I include screen.click() or screen.wait() in the script followed by screen.stop(), it doesn't work; I have to forcefully stop the script execution.
The text was updated successfully, but these errors were encountered:
I am using the following code for testing:
When I check the saved screenshots, I notice that the images show no changes despite switching screens during the test, which should reflect the current time.
I'm puzzled by this. I'm using Windows 11 as the client with SikuliX version 2.0.5 and Java version 17. The server is Fedora 22 with tigervnc-server version 1.6.0, and on the local machine (also Windows 11) with tigervnc-server version 1.13.1. Despite trying various configuration changes during testing, I haven't seen any differences in the results.
I also tried using the
screen.getClient().refreshFramebuffer();
method, but it didn't have any effect either.Furthermore, in my script, if I don't use the
screen.stop()
operation, the script does not naturally stop, and there are no error messages. Even if I includescreen.click()
orscreen.wait()
in the script followed by screen.stop(), it doesn't work; I have to forcefully stop the script execution.The text was updated successfully, but these errors were encountered: