sikuli-driver team mailing list archive

[Andreas Balogh <880861@xxxxxxxxxxxxxxxxxx>]

Well, I got proper recognition working after extensively playing by
a) reducing pattern size, and
b) adding .similar(0.97) - 0.96 and 0.98 do not work.

In Sikuli 0.10.2 pattern recognition (same code without similar and
pattern consisting of the complete pushbutton) worked without tweaking -
much easier to handle.

Compared to Sikuli 0.10.2 pattern recognition is DIFFICULT to get right.

So I'd consider this a regression bug. Does it make sense to restore
0.10.2 recognition in 1.0?

Much of the fun using Sikuli is gone if recognition becomes unreliable
and works only after spending a lot of time on tweaking the pattern and
.similar(x).

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/880861

Title:
  findAll() with multiple matches returns invalid last match

Status in Sikuli:
  New

Bug description:
  1. Sikuli 1.0 rc3
  2. Windows XP SP3 32-bit
  3. Enclosed code loops over all "Apply" boxes. Once apply has been clicked it wait for a confirmation box to appear, confirms, waits for the confirmation box to disappear. The final match does not point to the bitmap.
  4. Required bitmaps attached.

  # setFindFailedResponse(PROMPT)
  setROI(Screen(0))

  applies = findAll("Apply.png")

  
  for apply in applies:
      click(apply)
      confirm="Doyoureallyw-1.png"
      wait(confirm)
      click(Pattern("YesNo.png").targetOffset(-31,-1))
      waitVanish(confirm)

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/880861/+subscriptions