Question #200752 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/200752
RaiMan proposed the following answer: --- The bug is *in* the design, if you will. Fully agreed. Looking from this point of view, there are still many more design bugs in this on the other hand neat piece of software ;-) --- seemed to be an artifact of the OCR process When Sikuli started, the captured images where all named with the timestamps. Starting with Sikuli X and the availability of OCR, there are 3 options selectable in the IDE settings 1. trying to excerpt some text from the image and use it as name (the standard) 2. name the images yourself with a popup pre-filled with the name from 1 (my preferred option) 3. the old one with the timestamp option 1 has the problem, that different captures might yield the same filename, so the IDE adds -n to the filename. This additionally happens every time, when you grab a new image for an existing thumbnail, since it is most probable, that it generates the same filename. Since most people grab the same image multiple times in a find-click- wait workflow, instead of storing/using a match or getLastMatch(), you might get many filenames "some text-xx.png". Some of them are still used, some of them might get obsolete. -- 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 : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
