** Changed in: sikuli
Status: Fix Committed => Won't Fix
** Changed in: sikuli
Importance: High => Undecided
** Changed in: sikuli
Milestone: 2.0.0 => None
** Summary changed:
- [request] waitVanish with parameter Region/Match should wait until region
content changes
+ [request] waitVanish with parameter Region/Match should wait until region
content changes --- use 1.1.4+ and observe
--
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 --- use 1.1.4+ and observe
Status in Sikuli:
Won't Fix
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
_______________________________________________
Mailing list: https://launchpad.net/~sikuli-driver
Post to : [email protected]
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
