sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #38090
[Bug 1582106] Re: Click() fails while it should return 0
** Description changed:
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.
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1582106
Title:
Click() fails while it should return 0
Status in Sikuli:
New
Bug 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").
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1582106/+subscriptions
References