sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #37846
[Bug 1553702] Re: find(wrong-parameter) should signal an exception and not stop the IDE --- fixed 1.1.1 2016-05-01+
** Summary changed:
- find(wrong-parameter) should signal an exception and not stop the IDE
+ find(wrong-parameter) should signal an exception and not stop the IDE --- fixed 1.1.1 2016-05-01+
** Changed in: sikuli
Importance: High => Critical
** Summary changed:
- find(wrong-parameter) should signal an exception and not stop the IDE --- fixed 1.1.1 2016-05-01+
+ [1.1.0] find(wrong-parameter) should signal an exception and not stop the IDE --- fixed 1.1.1 2016-05-01+
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1553702
Title:
[1.1.0] find(wrong-parameter) should signal an exception and not stop
the IDE --- fixed 1.1.1 2016-05-01+
Status in Sikuli:
Fix Committed
Bug description:
I dont understand why it's been so time consuming figuring out how to shift the mouse a few pixels to the right of a found image.
Lets say I can successfuly locate an image. After locating it, I want to click 150 pixels to the right of it.
This line of code terminates my program without warning:
find(sortedMatches[-1]).targetOffset(150,0)
is it really that difficult to click xpixels to the right of a found
image?
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1553702/+subscriptions
References