| 2010-11-26 13:09:46 |
Bruno Vieira |
bug |
|
|
added bug |
| 2010-11-26 13:10:18 |
Bruno Vieira |
description |
In order to improve image finding times, Sikuli could save together with an image some meta information about that image.
the meta information could have the following, for a start:
- last seen coordinates
- original coordinates
So whenever a new image is created, Sikuli would populate these fields.
whenever this image is called by a script, Sikluli would update these fields.
The idea is that whenever the script runs, it can start to look the image on the "last seen coordinates", then on the "original coordinates" and if both fail, the entire screen as it normally does.
I believe this specific Find of the image (using these fields) can be done with a small timing (1s or 2s) so that the script can start searching the entire screen with not much delay.
Best case scenario: Most of the times, a specific image appears on the same location as the last time or very close to it (the last know coordinates can be a bit bigger area than the actual image occupies to allow some variation).
Worst case scenario: the image appears always in differernt places of the screen, thus making Sikuli loose those one or two seconds defined above.
Ir order to get rid of the worst case scenario, Sikuli IDE would allow the user to define a "always search the entire screen" or "contextualized search based on last known location" - or whatever better names for this :) |
In order to improve image finding speed, Sikuli could save together with an image some meta information about that image.
the meta information could have the following, for a start:
- last seen coordinates
- original coordinates
So whenever a new image is created, Sikuli would populate these fields.
whenever this image is called by a script, Sikuli would update these fields.
The idea is that whenever the script runs, it can start to look the image on the "last seen coordinates", then on the "original coordinates" and if both fail, the entire screen as it normally does.
I believe this specific Find of the image (using these fields) can be done with a small timing (1s or 2s) so that the script can start searching the entire screen with not much delay.
Best case scenario: Most of the times, a specific image appears on the same location as the last time or very close to it (the last know coordinates can be a bit bigger area than the actual image occupies to allow some variation).
Worst case scenario: the image appears always in differernt places of the screen, thus making Sikuli loose those one or two seconds defined above.
Ir order to get rid of the worst case scenario, Sikuli IDE would allow the user to define a "always search the entire screen" or "contextualized search based on last known location" - or whatever better names for this :)
|
|
| 2011-01-12 09:50:18 |
RaiMan |
summary |
Feature request: Save original and last known location of image |
[request] Save original and last known location of image |
|
| 2011-01-19 11:40:33 |
RaiMan |
sikuli: importance |
Undecided |
Wishlist |
|
| 2013-02-22 07:24:02 |
RaiMan |
sikuli: status |
New |
In Progress |
|
| 2013-02-22 07:24:06 |
RaiMan |
sikuli: assignee |
|
RaiMan (raimund-hocke) |
|
| 2013-02-22 07:25:49 |
RaiMan |
tags |
find image information meta speed |
fkt-region |
|
| 2013-05-06 12:03:54 |
RaiMan |
sikuli: importance |
Wishlist |
High |
|
| 2013-05-06 12:03:57 |
RaiMan |
sikuli: milestone |
|
x1.1 |
|
| 2014-01-12 14:55:08 |
RaiMan |
sikuli: status |
In Progress |
Fix Committed |
|
| 2014-09-17 12:36:56 |
RaiMan |
sikuli: milestone |
1.1.0 |
1.2.0 |
|
| 2014-09-17 12:39:02 |
RaiMan |
description |
In order to improve image finding speed, Sikuli could save together with an image some meta information about that image.
the meta information could have the following, for a start:
- last seen coordinates
- original coordinates
So whenever a new image is created, Sikuli would populate these fields.
whenever this image is called by a script, Sikuli would update these fields.
The idea is that whenever the script runs, it can start to look the image on the "last seen coordinates", then on the "original coordinates" and if both fail, the entire screen as it normally does.
I believe this specific Find of the image (using these fields) can be done with a small timing (1s or 2s) so that the script can start searching the entire screen with not much delay.
Best case scenario: Most of the times, a specific image appears on the same location as the last time or very close to it (the last know coordinates can be a bit bigger area than the actual image occupies to allow some variation).
Worst case scenario: the image appears always in differernt places of the screen, thus making Sikuli loose those one or two seconds defined above.
Ir order to get rid of the worst case scenario, Sikuli IDE would allow the user to define a "always search the entire screen" or "contextualized search based on last known location" - or whatever better names for this :)
|
1.1.0: partly implemented with new Image class (last match location is stored and checked first at subsequent searches)
1.2: make it persistent including the information where it was captured
-------------------------------------------------------------------
In order to improve image finding speed, Sikuli could save together with an image some meta information about that image.
the meta information could have the following, for a start:
- last seen coordinates
- original coordinates
So whenever a new image is created, Sikuli would populate these fields.
whenever this image is called by a script, Sikuli would update these fields.
The idea is that whenever the script runs, it can start to look the image on the "last seen coordinates", then on the "original coordinates" and if both fail, the entire screen as it normally does.
I believe this specific Find of the image (using these fields) can be done with a small timing (1s or 2s) so that the script can start searching the entire screen with not much delay.
Best case scenario: Most of the times, a specific image appears on the same location as the last time or very close to it (the last know coordinates can be a bit bigger area than the actual image occupies to allow some variation).
Worst case scenario: the image appears always in differernt places of the screen, thus making Sikuli loose those one or two seconds defined above.
Ir order to get rid of the worst case scenario, Sikuli IDE would allow the user to define a "always search the entire screen" or "contextualized search based on last known location" - or whatever better names for this :) |
|
| 2019-04-14 15:11:40 |
RaiMan |
sikuli: status |
Fix Committed |
In Progress |
|
| 2019-04-14 15:11:44 |
RaiMan |
sikuli: importance |
High |
Medium |
|
| 2019-04-14 15:11:49 |
RaiMan |
sikuli: milestone |
2.0.0 |
1.1.4 |
|
| 2019-07-14 10:51:18 |
RaiMan |
summary |
[request] Save original and last known location of image |
[request] Save original and last known location of image to be used in the next script execution (performance!) |
|
| 2019-07-15 08:23:10 |
RaiMan |
sikuli: importance |
Medium |
Wishlist |
|
| 2019-11-07 16:07:08 |
RaiMan |
sikuli: milestone |
1.1.4 |
2.1.0 |
|
