sikuli-driver team mailing list archive

Thread
Date

[Bug 532519] Re: [request] Exception FindFailed: last successful match and last screenshot should be accessible

To: sikuli-driver@xxxxxxxxxxxxxxxxxxx
From: RaiMan <rmhdevelop@xxxxxx>
Date: Thu, 21 Feb 2013 19:00:13 -0000
Reply-to: Bug 532519 <532519@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: sikuli
       Status: New => In Progress

** Changed in: sikuli
   Importance: Wishlist => Medium

** Changed in: sikuli
     Assignee: (unassigned) => RaiMan (raimund-hocke)

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/532519

Title:
  [request] Exception FindFailed: last successful match and last
  screenshot should be accessible

Status in Sikuli:
  In Progress

Bug description:
  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"))

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/532519/+subscriptions