sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

Thanks for the hint ;-)

The IDE (meaning sikuli-ide.jar) is no longer intended to run scripts
from command line. This is the job of sikuli-script.jar.

Nevertheless might it be of value in some situation to start the IDE with some command line parameters, that are available in the IDE, when running scripts as a global sys.argv.
This will be available plus the feature to edit these command line parameters prior to a script run in the IDE specific for each tab.

I plan to have something like the Maven pom's as
configuration/preferences/setup/preset for the IDE and sikuli-script
(XML or JSON format): if such a sikuli.config is in the same directory
as the script or given by some commandline parameter, it will be used in
this sense.

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

Title:
  [1.0] Command line arguments cut off

Status in Sikuli:
  Fix Committed

Bug description:
  Hello,

  Sorry if this has been reported or fixed already, but it appears I am
  having issues running scripts with a few command line parameters.

  For instance:

  C:\Windows\system32>c:\Sikuli\Sikuli\sikuli-script.cmd -j6 -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -te Cash -sa -c -re
  -Xms64M -Xmx512M -Dfile.encoding=UTF-8
  -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -te Cash -sa
  +++ using as SIKULIX_HOME: c:\Sikuli\Sikuli\

  Note the actual command I use is being truncated. This isn't a visual
  thing only, those parameters actually were not passed.

  What's interesting, is this seems like a maximum character thing, as
  opposed to maximum arguments. For instance if I remove the "-te Cash"
  part, I get "room" for two extra command line arguments:

  C:\Windows\system32>c:\Sikuli\Sikuli\sikuli-script.cmd -j6 -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -sa -c -re
  -Xms64M -Xmx512M -Dfile.encoding=UTF-8
  -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -sa -c -re
  +++ using as SIKULIX_HOME: c:\Sikuli\Sikuli\
  +++ this Sikuli version is 32-Bit

  Could this be fixed for 1.1? If a temporary fix or workaround is
  available that I or others who stumble upon this issue have, that'd be
  awesome too.

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