[request] make X 1.0 pattern matching backwards compatible with 0.10.2
Bug #887016 reported by
Andreas Balogh
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| SikuliX |
Won't Fix
|
Undecided
|
RaiMan | ||
Bug Description
bug 885617 (waitVanish/
| description: | updated |
Revision history for this message
| RaiMan (raimund-hocke) wrote | #1 |
| description: | updated |
| Changed in sikuli: | |
| status: | New → Won't Fix |
| assignee: | nobody → RaiMan (raimund-hocke) |
To post a comment you must log in.
Both mentioned bugs are requests, to optimize the X-1.0 VisionEngine to behave in a way, that one might expect. The need was hidden by the behavior of 10.2
Both are not requests for backward compatibility to the behavior of 10.2, but a reaction on situations that showed the outcome of a dramatically improved VisionEngine compared to the situation in 10.2
The difference between the two engines in that specific case seems to be, that in X-1.0 the default minimum similarity should be raised from 0.7 to a higher value towards 0.9, to get the same results as in 10.2
Both requests, make sense regarding ease of use and convenience.
I do not think, that it makes sense, to have two vision engines available to support a "backward compatibility", that is only motivated by a few cases of changed behavior.
I think, the migration from 10.2 to X-1.0 is neither supported nor documented at all, although the mentioned situations could have been foreseen by those who knew the impacts of the improvement.
With other software getting a major revision with impacts on features and behavior, you normally get some information on possible issues and how to solve the situations. This is missing with Sikuli.
In this sense, I do not support the request bug. Instead, there should be some more information on differences between 10.2 and X-1.0 and how to overcome critical situations (I will start a faq on that)