sikuli-driver team mailing list archive

[Emil Börjesson <750223@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I have implemented a script hierarchy structure of scripts with a master
script that imports a set of slave-scripts. Each slave-script has three
methods, called A(),B() and C(). The master-script uses a simple for-
loop to execute A(), B() and C() in each slave-script iteratively. Hence
slave-script 1 A() is run first, then slave-script 1 B() and so on until
slave-script N C() is finally executed.

Code snippet of the master-script:

<the necessary code to do imports>

import script1
import script2

scriptList = (script1,script2)

#slave-script execution loop
try:
	for script in scriptList:
		script.A()
		script.B()
		script.C()
except:
	print("Error")

The problem I have encountered is that if one of the slave-scripts casts
an exception, due to anything really, like a missing colon or a missing
image, and you fix the problem in the slave-script so that it works
correctly, the master script still uses the old broken implementation of
the slave-script. Hence, fixing a broken slave-script has no effect, the
entire script hierarchy is still broken. The only solution I have found
so far is to restart Sikuli with the corrected slave-scripts and re-run
the master-script. It seems that the IDE is cashing the old broken
slave-scripts and doesn't recognize that they have been changed (fixed).

1. Sikuli version: Sikuli X-1.0rc2
2. OS: Mac OS 10.6.4 64-bit
3. Produce the bug: See above description
4. Locate the bug: See above description

** Affects: sikuli
     Importance: Undecided
         Status: New

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

Title:
  Bug fixes in imported scripts not recognized by IDE

Status in Sikuli:
  New

Bug description:
  I have implemented a script hierarchy structure of scripts with a
  master script that imports a set of slave-scripts. Each slave-script
  has three methods, called A(),B() and C(). The master-script uses a
  simple for-loop to execute A(), B() and C() in each slave-script
  iteratively. Hence slave-script 1 A() is run first, then slave-script
  1 B() and so on until slave-script N C() is finally executed.

  Code snippet of the master-script:

  <the necessary code to do imports>

  import script1
  import script2

  scriptList = (script1,script2)

  #slave-script execution loop
  try:
  	for script in scriptList:
  		script.A()
  		script.B()
  		script.C()
  except:
  	print("Error")

  The problem I have encountered is that if one of the slave-scripts
  casts an exception, due to anything really, like a missing colon or a
  missing image, and you fix the problem in the slave-script so that it
  works correctly, the master script still uses the old broken
  implementation of the slave-script. Hence, fixing a broken slave-
  script has no effect, the entire script hierarchy is still broken. The
  only solution I have found so far is to restart Sikuli with the
  corrected slave-scripts and re-run the master-script. It seems that
  the IDE is cashing the old broken slave-scripts and doesn't recognize
  that they have been changed (fixed).

  1. Sikuli version: Sikuli X-1.0rc2
  2. OS: Mac OS 10.6.4 64-bit
  3. Produce the bug: See above description
  4. Locate the bug: See above description