Question #232844 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/232844
Status: Open => Answered
RaiMan proposed the following answer:
- the standard place, Sikuli looks for given images is in the bundle path,
which is the folder of the source (xxx.sikuli)
- you can get this folder by using getBundlePath() (e.g. to store it for later
restore, or just to know where you are)
- you can always set the bundle path to any other folder at runtime. Sikuli
will search there for images from now on until another bundle path is set
So the bundle path is the one place, where Sikuli searches for images at
any time and it must point to the folder, taht contains the image files
(Sikuli does not look into subfolders).
The image path is a collection of more than one path (actually the
bundle path is image path[0], since Sikuli internally always looks for
images along this path (which is the reason for the "automagic" import
of .sikuli and still finding all images)).
So the image path is a list of places, that is searched for images until
one is found in one of these places (first found wins, so sequence of
paths is relevant and you need some naming convention)
So in your case it depends on the usage of the subfolders, what is the best
choice:
- sequential usage: setBundlePath()
- concurrent usage: use image path feature
But I just thought, it might be a good idea, to allow one folder to be set as
bundle path and Sikuli will search all contained subfolders for an image file.
I will put it on the request list.
e.g. setBundlePath(some_folder, tree=true)
--
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
