| 2016-05-16 07:23:31 |
Alex Lunyov |
bug |
|
|
added bug |
| 2016-05-16 07:36:23 |
Alex Lunyov |
description |
Hi,
I'm using both last 1.1.0 and beta 1.1.1 versions SikuliX, Windows 7 64 bit.
SukuliX help says click() "returns the number of performed clicks (actually 1). A 0 (integer null) means that because of some reason, no click could be performed (in case of PS may be not Found)". But in my case it fails instead of returning 0 ("FindFailed"). |
Hi,
I'm using both last 1.1.0 and beta 1.1.1 versions SikuliX, Windows 7 64 bit.
SukuliX help says click() "returns the number of performed clicks (actually 1). A 0 (integer null) means that because of some reason, no click could be performed (in case of PS may be not Found)". But in my case it fails instead of returning 0 (now it unexpectedly reports "FindFailed"). |
|
| 2016-05-16 17:25:32 |
Alex Lunyov |
description |
Hi,
I'm using both last 1.1.0 and beta 1.1.1 versions SikuliX, Windows 7 64 bit.
SukuliX help says click() "returns the number of performed clicks (actually 1). A 0 (integer null) means that because of some reason, no click could be performed (in case of PS may be not Found)". But in my case it fails instead of returning 0 (now it unexpectedly reports "FindFailed"). |
Well,
Hi,
I'm using both last 1.1.0 and beta 1.1.1 versions SikuliX, Windows 7 64 bit.
SukuliX help says click() "returns the number of performed clicks (actually 1). A 0 (integer null) means that because of some reason, no click could be performed (in case of PS may be not Found)". But in my case it fails instead of returning 0 (now it unexpectedly reports "FindFailed"). |
|
| 2016-05-16 17:29:36 |
Alex Lunyov |
description |
Well,
Hi,
I'm using both last 1.1.0 and beta 1.1.1 versions SikuliX, Windows 7 64 bit.
SukuliX help says click() "returns the number of performed clicks (actually 1). A 0 (integer null) means that because of some reason, no click could be performed (in case of PS may be not Found)". But in my case it fails instead of returning 0 (now it unexpectedly reports "FindFailed"). |
Hi,
I'm using both last 1.1.0 and beta 1.1.1 versions SikuliX, Windows 7 64 bit.
SukuliX help says click() "returns the number of performed clicks (actually 1). A 0 (integer null) means that because of some reason, no click could be performed (in case of PS may be not Found)". But in my case it fails instead of returning 0 (now it unexpectedly reports "FindFailed"). |
|
| 2016-05-16 17:49:32 |
Alex Lunyov |
description |
Hi,
I'm using both last 1.1.0 and beta 1.1.1 versions SikuliX, Windows 7 64 bit.
SukuliX help says click() "returns the number of performed clicks (actually 1). A 0 (integer null) means that because of some reason, no click could be performed (in case of PS may be not Found)". But in my case it fails instead of returning 0 (now it unexpectedly reports "FindFailed"). |
Hi,
I'm using both last 1.1.0 and beta 1.1.1 versions SikuliX, Windows 7 64 bit.
SukuliX help says click() "returns the number of performed clicks (actually 1). A 0 (integer null) means that because of some reason, no click could be performed (in case of PS may be not Found)". But in my case it fails instead of returning 0 (now it unexpectedly reports "FindFailed").
P.S. Well, that's quite reasonable to throw out when this exception raises.
I just understood one need to use try/exception to handle this.
:) I'm new to this bug tracker, no idea how to delete myself solved "bug" from here. |
|
| 2021-02-09 15:21:51 |
RaiMan |
sikuli: status |
New |
Confirmed |
|
