sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

Public bug reported:

Hi,
I trigger my Sikuli script via command line in a batch file (I use 64-bit Windows 7 machine with Java 7 installed on it). With the earlier version of Sikuli, I used the following command to execute my script:

"C:\Program Files (x86)\Sikuli X\Sikuli-IDE-w.bat" -r
"C:\ABP\Executables\skl-files\Refresh-Batches.skl" > C:\ABP\Logs
\Refresh-Batches.log

I am using the print function at various places in my script to help me
create a log of events that happened when running my script. When
running my script from command line, I am redirecting this information
to a log file, which I examine after the execution of the script.

Now, after upgrading to Sikuli 1.0.1, I am using the following command to execute my script from command line:
 
"C:\Sikuli-64-Bit\runIDE.cmd" -r "C:\ABP\Executables\skl-files\Register-Files.skl" > C:\ABP\Logs\Register-Files.log

The script is running fine. The only change in behavior that I see is:
In the earlier version of sikuli, if there is a run time error, the error pops up in a dialog box and that gives me a visual confirmation that the script has stopped executing. In the latest version of of sikuli, the run time error is not being popped up in a dialog box. Instead it is being redirected to my log file. Hence, I am not knowing (immediately) that the script has stopped executing. 

Is there a way to bring back the old behavior in this version of sikuli.
I find the old behavior much more helpful.

Thanks,
Rafiq

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

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

Title:
  [request] want crash notification as popup, when running from command
  line.

Status in Sikuli:
  Fix Committed

Bug description:
  Hi,
  I trigger my Sikuli script via command line in a batch file (I use 64-bit Windows 7 machine with Java 7 installed on it). With the earlier version of Sikuli, I used the following command to execute my script:

  "C:\Program Files (x86)\Sikuli X\Sikuli-IDE-w.bat" -r
  "C:\ABP\Executables\skl-files\Refresh-Batches.skl" > C:\ABP\Logs
  \Refresh-Batches.log

  I am using the print function at various places in my script to help
  me create a log of events that happened when running my script. When
  running my script from command line, I am redirecting this information
  to a log file, which I examine after the execution of the script.

  Now, after upgrading to Sikuli 1.0.1, I am using the following command to execute my script from command line:
   
  "C:\Sikuli-64-Bit\runIDE.cmd" -r "C:\ABP\Executables\skl-files\Register-Files.skl" > C:\ABP\Logs\Register-Files.log

  The script is running fine. The only change in behavior that I see is:
  In the earlier version of sikuli, if there is a run time error, the error pops up in a dialog box and that gives me a visual confirmation that the script has stopped executing. In the latest version of of sikuli, the run time error is not being popped up in a dialog box. Instead it is being redirected to my log file. Hence, I am not knowing (immediately) that the script has stopped executing. 

  Is there a way to bring back the old behavior in this version of
  sikuli. I find the old behavior much more helpful.

  Thanks,
  Rafiq

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