sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #54168
[Bug 1863949] Re: [2.0.2] VNC: capture() returns ScreenImage instead of filename
Sorry for the inconvenience, but VNC is not well documented and not my
priority in the moment.
You have to live with your workaround.
I would suggest to isolate your VNC.capture() into a global function, so
you can easily adapt when changes are coming with 2.1.0.
looks a bit odd, but this is a oneliner:
imagePath = VNC.capture().getFile(FULL_PATH, "temp")
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1863949
Title:
[2.0.2] VNC: capture() returns ScreenImage instead of filename
Status in Sikuli:
In Progress
Bug description:
In 2.0.2, on 64 bit Arch Linux, depending on how capture is called it
is no longer returning a file path. I cannot find anywhere where this
behavior is documented and therefore am reporting it as a bug. It
seems to be returning a java object and making a java call.
imagePath = SCREEN.capture()
print imagePath
imagePath = VNC.capture()
print imagePath
imagePath = capture(VNC) #FYI - local screen captured
print imagePath
exit(0)
Actual:
CConnection: Server supports RFB protocol version 3.8
CConnection: Using RFB protocol version 3.8
org.sikuli.script.ScreenImage@59ab5f32
org.sikuli.script.ScreenImage@4236bae8
[info] Exit code: 0
/tmp/Sikulix_1686686143/sikuliximage-1582144646621.png
Expected:
shutil.move(vnc.capture(), FULL_PATH) #from tmp
Work around:
img = vnc.capture().saveInBundle("temp")
shutil.move(img, FULL_PATH) #from bundle
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1863949/+subscriptions
References