[1.1.1] findAll() should throw FindFailed --- fixed: 2017-03-29

Bug #1677134 reported by RaiMan on 2017-03-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sikuli
Critical
RaiMan

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.

RaiMan (raimund-hocke) on 2017-03-29
Changed in sikuli:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → RaiMan (raimund-hocke)
milestone: none → 1.1.1
RaiMan (raimund-hocke) on 2017-03-29
Changed in sikuli:
importance: High → Critical
summary: - [1.1.1] findAll() should throw FindFailed
+ [1.1.1] findAll() should throw FindFailed --- fixed: 2017-03-29
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers