| 2010-03-05 09:54:12 |
RaiMan |
bug |
|
|
added bug |
| 2010-03-05 09:55:01 |
RaiMan |
tags |
|
findfailed history |
|
| 2010-03-05 09:56:17 |
RaiMan |
description |
more a feature request:
especially for long running, unattended scripts its vital, to have as much information available in case of FindFailed.
In the moment (and for 0.10) the implementation of find.region would be None in this case. Since it would be helpful to know the last success, there should be some history information available.
e.g. find.last could reference the last successful match object
On top, if there would be a (maybe limited) stack like find.history, where the last successful match would be pushed in, you would have access to what happened in case of failure, without additional coding in the script.
now you have to code:
try:
mTrack = find()
click(mTrack)
mTrack = wait()
mTrack = find()
click(mTrack)
.... and so on
except FindFailed:
scrFile = str(mTrack)[str(mTrack).index("@")+1:] # scrShot filename of last success
in 0.10 with a find.last this could look very nice and easy:
import sys
try:
click()
wait()
click()
.... and so on
except FindFailed:
scrFile = str(find.last)[str(find.last).index("@")+1:]
To have a history, you have to add at least some push to every statement (with 0.10):
history = []
find(); history += [find.region]
click(); history += [find.region]
...
So to have it built-in would be much nicer. |
more a feature request:
especially for long running, unattended scripts its vital, to have as much information available in case of FindFailed.
In the moment (and for 0.10) the implementation of find.region would be None in this case. Since it would be helpful to know the last success, there should be some history information available.
e.g. find.last could reference the last successful match object
On top, if there would be a (maybe limited) stack like find.history, where the last successful match would be pushed in, you would have access to what happened in case of failure, without additional coding in the script.
now you have to code:
try:
mTrack = find()
click(mTrack)
mTrack = wait()
mTrack = find()
click(mTrack)
.... and so on
except FindFailed:
scrFile = str(mTrack)[str(mTrack).index("@")+1:] # scrShot filename of last success
in 0.10 with a find.last this could look very nice and easy:
import sys
try:
click()
wait()
click()
.... and so on
except FindFailed:
scrFile = str(find.last)[str(find.last).index("@")+1:]
To have a history, you have to add at least some push to every statement (with 0.10):
history = []
find(); history += [find.region]
click(); history += [find.region]
...
So to have it built-in would be much nicer.
also motivated by bug report:
https://bugs.launchpad.net/sikuli/+bug/532105 |
|
| 2010-05-05 12:59:10 |
RaiMan |
summary |
Exception FindFailed: last successful match should be accessible |
Exception FindFailed: last successful match and last screenshot should be accessible |
|
| 2010-05-05 13:01:07 |
RaiMan |
description |
more a feature request:
especially for long running, unattended scripts its vital, to have as much information available in case of FindFailed.
In the moment (and for 0.10) the implementation of find.region would be None in this case. Since it would be helpful to know the last success, there should be some history information available.
e.g. find.last could reference the last successful match object
On top, if there would be a (maybe limited) stack like find.history, where the last successful match would be pushed in, you would have access to what happened in case of failure, without additional coding in the script.
now you have to code:
try:
mTrack = find()
click(mTrack)
mTrack = wait()
mTrack = find()
click(mTrack)
.... and so on
except FindFailed:
scrFile = str(mTrack)[str(mTrack).index("@")+1:] # scrShot filename of last success
in 0.10 with a find.last this could look very nice and easy:
import sys
try:
click()
wait()
click()
.... and so on
except FindFailed:
scrFile = str(find.last)[str(find.last).index("@")+1:]
To have a history, you have to add at least some push to every statement (with 0.10):
history = []
find(); history += [find.region]
click(); history += [find.region]
...
So to have it built-in would be much nicer.
also motivated by bug report:
https://bugs.launchpad.net/sikuli/+bug/532105 |
more a feature request: (updated after 0.10 released)
especially for long running, unattended scripts its vital, to have as much information available in case of FindFailed.
After an unsuccessful find getLastMatch() returns None. the lastMatch() should be left untouched, to be available in these cases.
On top, if there would be a (maybe limited) stack like region.findHistory (accessible with a region.getHistory() returning a list of matches), where the last successful match would be pushed in, you would have access to what happened in case of failure, without additional coding in the script.
in case of FindFailed the last screenshot should be available. (additional option saveScreenshotAtFindFailed("path-to-a-file"))
|
|
| 2010-05-05 13:01:20 |
RaiMan |
tags |
findfailed history |
0.10 findfailed history |
|
| 2011-01-12 10:08:02 |
RaiMan |
summary |
Exception FindFailed: last successful match and last screenshot should be accessible |
[request] Exception FindFailed: last successful match and last screenshot should be accessible |
|
| 2011-01-19 12:00:42 |
RaiMan |
sikuli: importance |
Undecided |
Wishlist |
|
| 2011-12-27 02:02:25 |
Ben Turner |
bug |
|
|
added subscriber Ben Turner |
| 2013-02-21 19:00:13 |
RaiMan |
sikuli: status |
New |
In Progress |
|
| 2013-02-21 19:00:17 |
RaiMan |
sikuli: importance |
Wishlist |
Medium |
|
| 2013-02-21 19:00:21 |
RaiMan |
sikuli: assignee |
|
RaiMan (raimund-hocke) |
|
| 2013-02-22 10:58:03 |
RaiMan |
tags |
0.10 findfailed history |
fkt-region |
|
| 2013-02-22 10:58:30 |
RaiMan |
tags |
fkt-region |
general |
|
| 2013-05-06 12:10:26 |
RaiMan |
sikuli: milestone |
|
x1.1 |
|
| 2014-01-12 18:32:27 |
RaiMan |
sikuli: milestone |
1.1.0 |
1.2.0 |
|
| 2019-11-07 16:27:11 |
RaiMan |
sikuli: milestone |
2.0.0 |
2.1.0 |
|
| 2019-11-07 16:27:22 |
RaiMan |
summary |
[request] Exception FindFailed: last successful match and last screenshot should be accessible |
[check] Exception FindFailed: last successful match and last screenshot should be accessible |
|
