sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

this is a known bug (but cannot find it right now :-(

Using similar(1.0) has some other oddities, so I use 0.99 instead in
those cases.

** Summary changed:

- X-1.0rc2: exact() information is lost in GUI on reopening
+ X-1.0rc2: exact() information is lost in GUI on reopening --- workaround

** Description changed:

+ **** workaround:
+ use similar(0.99) instead
+ ----------------------------------------------
+ 
  When a pattern is defined as exact match using 1.0 similarity in GUI, the image gets "1.0" marker and the .py file contains the following source:
-   img = Pattern("img.png").exact()
+   img = Pattern("img.png").exact()
  
  However, if you save and reopen Sikuli, the "1.0" marker is lost, and
  click on image resets similarity slider to a value of 0.7. This creates
  big trouble when debugging, because engine still matches the picture as
  exact() match and if PS doesn't have exact similarity, Matching Preview
  will show that there is no match until you move slider.
  
  Vista 32.

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

Title:
  X-1.0rc2: exact() information is lost in GUI on reopening ---
  workaround

Status in Sikuli:
  New

Bug description:
  **** workaround:
  use similar(0.99) instead
  ----------------------------------------------

  When a pattern is defined as exact match using 1.0 similarity in GUI, the image gets "1.0" marker and the .py file contains the following source:
    img = Pattern("img.png").exact()

  However, if you save and reopen Sikuli, the "1.0" marker is lost, and
  click on image resets similarity slider to a value of 0.7. This
  creates big trouble when debugging, because engine still matches the
  picture as exact() match and if PS doesn't have exact similarity,
  Matching Preview will show that there is no match until you move
  slider.

  Vista 32.