[2.0.1] observe: setInactive/setActive not working --- fixed with 2.0.2

Bug #1476773 reported by RaiMan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SikuliX
Fix Committed
Critical
RaiMan

Bug Description

Information about the fix: https://github.com/RaiMan/SikuliX1/issues/270
--------------------------------------------------------------------------

Hi again.

Im writting a code that will check if an image appeared on a Region. After the image appears the program will scan the same region to see if it desappears. When the image desappears it will start to scan to see if it appears again, and so on.

So, im using OnAppear and OnVanish on the same region with a single handler. (calling Repeat() in the end)

The problem with this solution is that the handler will continue to be called with type = APPEAR even if the handler was already triggered one time with APPEAR. The same happen when the image disappears and the handler is called with type = VANISH. It will continue to be called with VANISH until the image appears again.

Is there a way to avoid this? Is it possible to unregister OnAppear/OnVanish and register it again in a Region?
Do i have to use two different regions with the same dimmensions?

Thanks

Revision history for this message
RaiMan (raimund-hocke) wrote :

just to have it in my records ;-)

Changed in sikuli:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → RaiMan (raimund-hocke)
milestone: none → 1.1.0
RaiMan (raimund-hocke)
Changed in sikuli:
importance: High → Medium
milestone: 1.1.0 → 2.0.0
RaiMan (raimund-hocke)
summary: - [1.1.0] observe: setInactive/setActive not working
+ [1.1.0] observe: setInactive/setActive not working --- use 1.1.4+
Changed in sikuli:
status: Fix Committed → Fix Released
importance: Medium → Undecided
milestone: 2.0.0 → none
RaiMan (raimund-hocke)
Changed in sikuli:
status: Fix Released → In Progress
importance: Undecided → High
milestone: none → 2.0.2
summary: - [1.1.0] observe: setInactive/setActive not working --- use 1.1.4+
+ [2.0.1] observe: setInactive/setActive not working
summary: - [2.0.1] observe: setInactive/setActive not working
+ [2.0.1] observe: setInactive/setActive not working --- to be checked
RaiMan (raimund-hocke)
summary: - [2.0.1] observe: setInactive/setActive not working --- to be checked
+ [2.0.1] observe: setInactive/setActive not working --- fixed with 2.0.2
Changed in sikuli:
status: In Progress → Fix Committed
importance: High → Critical
RaiMan (raimund-hocke)
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.