sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

... but your idea makes some sense:
waitVanish(someRegion)

where someRegion is a Region or Match object could mean:
wait until the content of the region changes.

I make it a request bug, to have this convenience shortcut.

** Summary changed:

- [1.1.0] waitVanish crashes Sikuli when using Match objects created from find()
+ [request] waitVanish with parameter Region/Match should wait until region content changes

** Changed in: sikuli
       Status: New => Fix Committed

** Changed in: sikuli
   Importance: Undecided => High

** Changed in: sikuli
     Assignee: (unassigned) => RaiMan (raimund-hocke)

** Changed in: sikuli
    Milestone: None => 1.2.0

-- 
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