sikuli-driver team mailing list archive

[RaiMan <question184410@xxxxxxxxxxxxxxxxxxxxx>]

Question #184410 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/184410

RaiMan posted a new comment:
@Josh

--- challenge: pre/post transforms stored in the image name
I think, that file handling can be solved rather easy (no need to specify absolute path names):
-- all images in a group have to be in the same folder (which might be on Sikuli's image path and even in the net)
-- the root element of a group has to have the fixed structure:
resourceName__01-01
-- from this file you get the absolute path and with this the containing folder
-- both in Python and Java it is possible to read the directory and find the rest of the images belonging to the group

So when creating a multi-part pattern ( e.g. p =
MultiPattern(resourceName) ) no absolute path is needed and all the file
handling is inside the class MultiPattern.

--- so it is possible to do a delta transform.
Yes, many of these possible region transform functions are still missing in Sikuli.
Besides the ones you mentioned e.g. something like reg.belowIncluding().rightIncluding(), which now has to be built with:

reg.above(1).below().left(1).right()

works, but looks ugly.

--- Additionally being able to specify a limit on how far the region extends
I made some performance tests on this and found out, that there is not really a significant difference between specifying below() and below(100). For multi-part patterns you might support optimized searches by  a specific  element sequence (e.g. tl -> br and then all the other elements).

You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.