[request] waitVanish/onVanish should run with a default minimum similarity near 1.0

Bug #885617 reported by RaiMan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SikuliX
In Progress
Medium
RaiMan

Bug Description

Usually the intention of the user, when using waitVanish/onVanish, is to wait for a specific image to vanish.

This image usually is matched with a high similarity score (above 0.9 to 0.95).

If these methods work with the standard similarity of 0.7, the risk is high, that something is found on the screen, that is not intended, if the object has already vanished, with the consequence, that the script might hang.

The average user might not be aware of this situation, so it is a convenience to let these methods use e.g. 0.95 as standard.

Currently you have to specify a pattern with similarity set to an appropriate high value, to avoid these situations.

RaiMan (raimund-hocke)
Changed in sikuli:
importance: Undecided → Wishlist
RaiMan (raimund-hocke)
Changed in sikuli:
status: New → In Progress
assignee: nobody → RaiMan (raimund-hocke)
tags: added: fkt-region
RaiMan (raimund-hocke)
Changed in sikuli:
importance: Wishlist → High
milestone: none → x1.1
RaiMan (raimund-hocke)
tags: added: todo
RaiMan (raimund-hocke)
Changed in sikuli:
milestone: 1.1.0 → 1.2.0
RaiMan (raimund-hocke)
Changed in sikuli:
importance: High → Medium
milestone: 2.0.0 → 2.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.