Re: [Sikuli-driver] [Question #691154]: Transition from 1.1.0 to 2.0.4. Unexpected image search behavior

Question #691154 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/691154 Linked to bug: #1882947 https://bugs.launchpad.net/bugs/1882947 "[2.0.4] Image.getSub() does not work as expected from 1.1.0" -- You received this question notification because your team Sikuli

Re: [Sikuli-driver] [Question #691154]: Transition from 1.1.0 to 2.0.4. Unexpected image search behavior

Question #691154 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/691154 Darius Tumas gave more information on the question: Not sure is that intentional or not, but the problem seems is with: Image testImage = Image.create("image_name_in_classpath"); testImage.getSub(x, y, w, h)

Re: [Sikuli-driver] [Question #691154]: Transition from 1.1.0 to 2.0.4. Unexpected image search behavior

Question #691154 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/691154 Darius Tumas gave more information on the question: When i debug both images by saving them, they do exist, and they do have expected contents. OS: Windows 10 Java: OpenJDK 8 -- You received this question

Re: [Sikuli-driver] [Question #691154]: Transition from 1.1.0 to 2.0.4. Unexpected image search behavior

Question #691154 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/691154 Description changed to: As title states i'm converting my Java application from Sikuli 1.1.0 to 2.0.4. In 1.1.0 Following procedure was: 1. Create image from sprites sheet. 2. Crop to the spot of interest 3.