with setFindFailedResponse(SKIP) click(ImageNotFound) acts like a click() - should do nothing --- fixed 2017-07-26
Bug #1706361 reported by
Hieu Dao
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| SikuliX |
Fix Committed
|
Critical
|
RaiMan | ||
Bug Description
This issue is annoying because it clicks on mouse position if it doesn't find anything
Revision history for this message
| RaiMan (raimund-hocke) wrote Re: with setFindFailedResponse(SKIP) click(ImageNotFound) acts like a click() - should do nothing | #1 |
| summary: |
- skip click(setFindFailedResponse(SKIP) ) still does click on mouse - position + with setFindFailedResponse(SKIP) click(ImageNotFound) acts like a + click() - should do nothing |
| Changed in sikuli: | |
| status: | New → Fix Committed |
| importance: | Undecided → High |
| assignee: | nobody → RaiMan (raimund-hocke) |
| milestone: | none → 1.1.2 |
Revision history for this message
| RaiMan (raimund-hocke) wrote | #2 |
| Changed in sikuli: | |
| importance: | High → Critical |
| summary: |
with setFindFailedResponse(SKIP) click(ImageNotFound) acts like a - click() - should do nothing + click() - should do nothing --- fixed 2017-07-26 |
To post a comment you must log in.
in fact with latest version 1.1.1 it acts like Region.click() (clicks on last match or center).
Annoying - accepted, sorry ;-)
I will try to fix it as soon as possible.