Question #235137 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/235137
joseytw posted a new comment: Thank you for your prompt reply - I really appreciate you taking the time to read and respond to my post! After reading your response I just want to make sure I am clear on what it means. When you say: “There is no other solution available currently for images inside a jar, so your app would only work inside eclipse with regular image file names relative to the project folder.” It pretty much means that if I export my code as a runnable JAR that has images saved inside of it, that I will not be able to get Sikuli to use the images stored in that JAR file to match an image on-screen even if I use something like ‘this.getClass().getClassLoader().getResource(resouce)’ or try to point Sikulu to the images inside the JAR file using relative paths. As I understand it, my 2 options are: 1) Keep my images outside of the JAR file and point Sikuli at those using either String Patterns or BufferedImage patterns 2) Patiently wait for the BufferedImage fix to be implemented (I would be happy to wait by the way!) Is this correct? (Since I have spent so much time trying to get this to work I want to be very clear on what my options are moving forward. I know you are probably busy with a million things and I would like to thank you again for taking the time to help clarify things for me!) -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
