-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
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
[1.1.4] CvException when using find() in a project upgraded from 1.1.3 due to not supported png-image-type #21
Comments
Thanks for reporting. Can you send me the relevant java statement(s) (as short as possible), the offending image and a screenshot, where it should be found? if yes: sikulix--at--outlook--dot--com |
In this case the images where produced with the help of some online service, which produce png-images, that in SikuliX internally result in BufferedImage of TYPE_BYTE_INDEXED (RGB without transparency but with a special color model). |
Confirmed as resolved locally! Thanks again for the quick turnaround. |
Thanks for feedback. |
Hi Again RaiMan, just dropping in to ask when the Maven clone will be updated with this fix? I'm using Maven to simplify the build process on CI machines but the version found via Maven is from August. Thanks again. |
Uuups, sorry. Did not realize, that I left the OSSRH upload switched off after some testing. |
Being eager to make use of the both the improved OCR and the transparent masking, this week I upgraded an existing, in-progress project from 1.1.3 to 1.1.4 to attempt to make use of the new features.
Noticing that everything required is now bundled into one .jar file, I removed my old Sikuli 1.1.3 install directory & jar file, and imported the nightly build via maven. However, I can no longer run any of my tests using sikuli, because any attempt to find an image results in this error:
I'm unclear what could be causing this issue, as I'm not very clued up on the underlying opencv libraries, but I was previously able to make use of this exact image before so I don't believe that it is the issue unless a significant requirement for saved images has changed.
Eager to get to the bottom of this as, like I said, I'm excited to make use of the new stuff.
The text was updated successfully, but these errors were encountered: