[1.0.1 ok] Windows: Command line arguments cut off
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
Fix Committed
|
Critical
|
RaiMan |
Bug Description
--- fixed with 1.0.1
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\
-Xms64M -Xmx512M -Dfile.
-r c:\Sikuli\
+++ 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\
-Xms64M -Xmx512M -Dfile.
-r c:\Sikuli\
+++ 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.
description: | updated |
summary: |
- Command line arguments cut off + [1.0]Command line arguments cut off |
summary: |
- [1.0]Command line arguments cut off + [1.0] Command line arguments cut off |
tags: |
added: scriptrun removed: arguments |
summary: |
- [1.0] Command line arguments cut off + [1.0] Windows: Command line arguments cut off |
Changed in sikuli: | |
importance: | High → Critical |
description: | updated |
summary: |
- [1.0] Windows: Command line arguments cut off + [1.0.1 ok] Windows: Command line arguments cut off |
I will check and guess I will have fixed it already for the service update 1.0.1 end of July.
If I find any workaround earlier, I let you know.