sikuli-driver team mailing list archive

[RaiMan <sikulix@xxxxxxxxxxx>]

Public bug reported:

******************** workaround
After changing the global settings, you have to use
setFindFailedResponse(...)
setFindFailedHandler(...)
with the same settings, to update the settings of global object SCREEN

Another option is, to use
SCREEN = Screen()
afterwards, to force a recreation of the global SCREEN object.
------------------------------------------------------

When using
FindFailed.setFindFailedResponse and/or FindFailed.setFindFailedResponse

to specify some global FindFailed handling, then these global settings
will not be inherited by the global SCREEN object, because this is
instantiated once at IDE start or before scriptrun from commandline.

By design, these settings are only inherited by region objects newly
created during scriptrun.

We need a feature to tell SCREEN, that the global FindFailed settings
have changed.

** 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.3

** Description changed:

  When using
  FindFailed.setFindFailedResponse and/or FindFailed.setFindFailedResponse
  
  to specify some global FindFailed handling, then these global settings
  will not be inherited by the global SCREEN object, because this is
  instantiated once at IDE start or before scriptrun from commandline.
  
+ By design, these settings are only inherited by region objects newly
+ created during scriptrun.
+ 
  We need a feature to tell SCREEN, that the global FindFailed settings
  have changed.

** Description changed:

+ ******************** workaround
+ After changing the global settings, you have to use
+ setFindFailedResponse(...)
+ setFindFailedHandler(...)
+ with the same settings, to update the settings of global object SCREEN
+ 
+ Another option is, to use
+ SCREEN = Screen()
+ afterwards, to force a recreation of the global SCREEN object.
+ ------------------------------------------------------
+ 
  When using
  FindFailed.setFindFailedResponse and/or FindFailed.setFindFailedResponse
  
  to specify some global FindFailed handling, then these global settings
  will not be inherited by the global SCREEN object, because this is
  instantiated once at IDE start or before scriptrun from commandline.
  
  By design, these settings are only inherited by region objects newly
  created during scriptrun.
  
  We need a feature to tell SCREEN, that the global FindFailed settings
  have changed.

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

Title:
  [1.1.x] Python scripting: Global SCREEN object does not inherit global
  FindFailed settings

Status in Sikuli:
  Fix Committed

Bug description:
  ******************** workaround
  After changing the global settings, you have to use
  setFindFailedResponse(...)
  setFindFailedHandler(...)
  with the same settings, to update the settings of global object SCREEN

  Another option is, to use
  SCREEN = Screen()
  afterwards, to force a recreation of the global SCREEN object.
  ------------------------------------------------------

  When using
  FindFailed.setFindFailedResponse and/or FindFailed.setFindFailedResponse

  to specify some global FindFailed handling, then these global settings
  will not be inherited by the global SCREEN object, because this is
  instantiated once at IDE start or before scriptrun from commandline.

  By design, these settings are only inherited by region objects newly
  created during scriptrun.

  We need a feature to tell SCREEN, that the global FindFailed settings
  have changed.

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