sikuli-driver team mailing list archive

[RaiMan <sikulix@xxxxxxxxxxx>]

Public bug reported:

In the docs it says that findAll should cause a FindFailed exception if there are no matches in 1.1 (http://sikulix-2014.readthedocs.io/en/latest/region.html#Region.findAll). The actual behavior, however, seems to be that it returns a None object. I can make my code account for both, but which of these is the correct behavior moving forward?
(reported directly to RaiMan by Minyoung Choi)

All find operations (except exists by design) should report FindFailed
and support the FindFailed response concept.

** Affects: sikuli
     Importance: High
     Assignee: RaiMan (raimund-hocke)
         Status: Fix Committed

** Changed in: sikuli
       Status: New => Fix Committed

** Changed in: sikuli
   Importance: Undecided => High

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

** Changed in: sikuli
    Milestone: None => 1.1.1

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

Title:
  [1.1.1] findAll() should throw FindFailed

Status in Sikuli:
  Fix Committed

Bug description:
  In the docs it says that findAll should cause a FindFailed exception if there are no matches in 1.1 (http://sikulix-2014.readthedocs.io/en/latest/region.html#Region.findAll). The actual behavior, however, seems to be that it returns a None object. I can make my code account for both, but which of these is the correct behavior moving forward?
  (reported directly to RaiMan by Minyoung Choi)

  All find operations (except exists by design) should report FindFailed
  and support the FindFailed response concept.

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