← Back to team overview

sikuli-driver team mailing list archive

[Bug 1297168] [NEW] Feature request for a command like "exit(1)" that starts the script from a specific line

 

Public bug reported:

It would be extremely useful to have a command that will start executing my script from a specific line: like "start(1)"??
It would be like exit(1) which stops it at that line of the code, just the other way round..

Say if I want to test my 600 line script from line 101 to 120 I would put the command "start(1)" at line 100 and "exit(1)" at line 121.
This would be amazingly helpful for executing and testing parts of a code easily.

At the moment I have to copy and paste the parts of my script into a new
project to test and then modify the original with my corrections and
then copy the modified again to test it.. this process can slow down
quite a lot when I have hundreds of lines..

** 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/1297168

Title:
  Feature request for a command like "exit(1)" that starts the script
  from a specific line

Status in Sikuli:
  New

Bug description:
  It would be extremely useful to have a command that will start executing my script from a specific line: like "start(1)"??
  It would be like exit(1) which stops it at that line of the code, just the other way round..

  Say if I want to test my 600 line script from line 101 to 120 I would put the command "start(1)" at line 100 and "exit(1)" at line 121.
  This would be amazingly helpful for executing and testing parts of a code easily.

  At the moment I have to copy and paste the parts of my script into a
  new project to test and then modify the original with my corrections
  and then copy the modified again to test it.. this process can slow
  down quite a lot when I have hundreds of lines..

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


Follow ups

References