sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #29144
[Bug 1389432] Re: [1.1.0] waitVanish crashes Sikuli when using Match objects created from find()
the java docs from waitVanish:
/**
* waits until target vanishes or timeout (in seconds) is
* passed (AutoWaitTimeout)
*
* @param <PSI> Pattern, String or Image
* @param target The target to wait for it to vanish
* @return true if the target vanishes, otherwise returns false.
public <PSI> boolean waitVanish(PSI target) {
in version 1.0.1 using any other kind of parameter (like in your case a
Match object as a result from find(image)) should have evaluated to an
error message: image file not found on disk.
This is irritating, so in 1.1.0 it correctly reports wrong parameter in
your case.
If you want to wait for an image to vanish, that just was found (in 1.1.0):
waitVanish(find(image).getImage())
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1389432
Title:
[request] waitVanish with parameter Region/Match should wait until
region content changes
Status in Sikuli:
Fix Committed
Bug description:
When I have a region that I define as using find(), for some reason
when I call waitVanish on that region it crashes Sikuli (ie,
waitVanish(img.find(img2)) or waitVanish(find(img)). Didn't have this
problem before on 1.0.1.
Here's the debug logs:
[debug] Region: waiting for M[92,339 212x32]@S(S(0)[0,0 1280x800]) S:1.00 C:198,355 [6/6 msec] to vanish
[error] Region: doFind: invalid parameter: M[92,339 212x32]@S(S(0)[0,0 1280x800]) S:1.00 C:198,355 [6/6 msec]
[error] ***** Terminating SikuliX after a fatal error 999 *****
It makes no sense to continue!
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1389432/+subscriptions
References