sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

yes, good finding. I did not think about this possible cause.

import of a .sikuli does the following:
- find the .sikuli on sys.path
- tell Jython import to import the contained .py file
- add the folder to the end of the image path (the main running script is always on first position)

When running and searching image files, these image path folders are
searched from first entry to last: first found wins

So having identical image file names in different .sikuli, that might
import each other can be used intelligently, but with no intention, this
is a high risk for errors like yours.

The docs recommend, to have a naming scheme for the image file names in
case of more complex import usages.

With the new version 1.0.1 using -d 3 as runtime option will show in the
log, which image files are used.

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

Title:
  Image similarity value changes randomly

Status in Sikuli:
  Opinion

Bug description:
  When images are first captured, they have a similarity value of 1.0,
  and match exactly. However, when a script is run later, the similarity
  value for images degrades, typically to a value of ~.6, despite the
  exact same screen being visible. It occurs seemingly at random;
  typically it takes several days before an image will no longer be
  recognized, but it can occur faster as well. Because of the random
  nature of the error, it is difficult to reproduce intentionally, but
  seems to occur very frequently when scripts are tested at a later date
  or on a different client machine.

  Sikuli: 1.0.0
  OS: Windows 7 32-bit

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