We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original author: [email protected] (June 13, 2013 12:14:26)
Hi sikuli team !
sikuli script was throwing a findfail exception when no match were found on the screen whereas sikuli API simply returns a null match pointer.
Is there any philosophical/design reason behind this change of behavior ?
Can a flag (to switch between those two behaviors) be considered a new feature ?
Thanks
Original issue: http://code.google.com/p/sikuli-api/issues/detail?id=62
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Original author: [email protected] (June 13, 2013 12:14:26)
Hi sikuli team !
sikuli script was throwing a findfail exception when no match were found on the screen whereas sikuli API simply returns a null match pointer.
Is there any philosophical/design reason behind this change of behavior ?
Can a flag (to switch between those two behaviors) be considered a new feature ?
Thanks
Original issue: http://code.google.com/p/sikuli-api/issues/detail?id=62
The text was updated successfully, but these errors were encountered: