This only happened in the past with changed code, that is imported by a
main script, if both are open in IDE.

fixed: see docs:
http://sikulix-2014.readthedocs.io/en/latest/scripting.html#importing-other-sikuli-scripts-reuse-code-and-images

... and read carefully to the end of the chapter.

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

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

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

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

** Summary changed:

- After modifying and saving some code in sikuli IDE for existing test, when 
Run button is clicked , IDE continues to use the older version of the code for 
execution.
+ After modifying and saving some code in sikuli IDE for existing test, when 
Run button is clicked , IDE continues to use the older version of the code for 
execution. --- fixed in 1.1.1 final

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

Title:
  After modifying and saving some code in sikuli IDE for existing test,
  when Run button is clicked , IDE continues to use the older version of
  the code for execution. --- fixed in 1.1.1 final

Status in Sikuli:
  Fix Committed

Bug description:
  After modifying and saving some code in sikuli IDE for existing test,
  when Run button is clicked , IDE continues to use the older version of
  the code for execution.

  The IDE has to be closed and reopened again to reflect the changes.

  Other work around for this issue is triggering test via command
  prompt.

  Team, can you please fix this issue.

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

_______________________________________________
Mailing list: https://launchpad.net/~sikuli-driver
Post to     : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp

Reply via email to