← Back to team overview

sikuli-driver team mailing list archive

[Bug 1240001] Re: setting a new similarity have no effect

 

I tested with your 2 buttons (since one is enabled while the other is
disabled)

For the test I chose the image of the trailing letters "ar", which are
available in both buttons.

I confirm for version 1.0.1, that when using images of the button text
only (as you do) with more or less of the gray background around, you
get a score of 1.0 in all cases. So this approach cannot be used to
distinguish between the 2 button states (which I guess you want to do).

But if you make shots, that contain at least the upper and/or lower
button border (white or black line), these images give significantly
different scores (should match 1.0, should not match <0.8).

When I started to develop the SikuliX 1.0+ versions, I started with a
codebase from SikuliX-1.0, that was already changed against RC3 by the
former developer, especially in the area of greyscaled images and
recognizing text. I guess this is the reason, why you now get this
different results.

as a workaround, you have to make shots, that at least contain one of
the upper/lower button borders.

I leave this as a bug, since it is a difference to RC3 and I will check,
when I get down to image matching in late November.

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

Title:
  [1.0.1] grayscale shots always result in score 1.0 if they do not
  contain real black or white elements

Status in Sikuli:
  Confirmed

Bug description:
  1. Version of Sikuli: X-1.0.1
  2. Operating system: Windows XP Pro SP3
  3. Procedure to reproduce the bug: 

          a - Create a script containing the following code
  (button_enable.png is attached)

                Settings.MinSimilarity = 0.99
                click("C:/button_enable.png")

          b - Open the attached image button_disabled.png and run the
  script above

          --> Result: The "click" is performed while it should not

  4. This problem does not appear with Sikuli X-rc3

  
  Best regards
  Pierre Dumas

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


References