[1.1.4] findText changed behaviour: less reliable than in 1.1.3
Bug #1834341 reported by
anson-fang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
Fix Released
|
Medium
|
RaiMan |
Bug Description
could you help to fix the accuracy for method "findText"?
when update sikuli from version 1.1.2 to the latest version. I found the method "findText" is not unstable, compared with older version. We have many scripts by finding element by findText and they work normally, but when I update sikuli to latest version 1.1.4. It can't find element Frequently.
environment : java 8/ mac 10.14/
BTW is there any road map for sikuli 1.1.4?
description: | updated |
description: | updated |
summary: |
- findbyText for sikuli 1.1.4 is not unstable + method findText for sikuli 1.1.4 is not unstable |
summary: |
- method findText for sikuli 1.1.4 is not unstable + [1.1.4] findText changed behaviour: less reliable than in 1.1.3 |
Changed in sikuli: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → RaiMan (raimund-hocke) |
milestone: | none → 1.1.4 |
Changed in sikuli: | |
status: | In Progress → Fix Released |
milestone: | 1.1.4 → 2.0.0 |
To post a comment you must log in.
The implementation of the text features (find and read) is completely revised in 1.1.4 and is based on:
- Tesserract (https:/ /github. com/tesseract- ocr/tesseract) version 3.05
- Tess4J (https:/ /github. com/nguyenq/ tess4j) version 3.5
There are surely many things that might be worth to optimise, but the text feature in SikuliX currently runs with low development priority.
So in case you have to stick with 1.1.3, if you find it is working more reliable in your use cases.
Feel free, to attach a documentation of different behaviour in 1.1.4 here in this bug though.