sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #21472
Re: [Question #236682]: Sikuli failing to run script or executable when launched from command line or double clicked
Question #236682 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/236682
kinetik posted a new comment:
Ok, so I just tried it that way too and got this error below. But I
think I found the answer—it's the number in the path name followed by a
space. I can't even escape the space after the number and have it work.
TEST 1 (quoted path):
$ /Applications/SikuliX-IDE.app/Contents/runIDE -r "/Volumes/GraphicsXRaid/04 Elements/_AE_Scripts_Effects/scripts from Kevin/Index Comps From Projects/Suppress_AE_Dialogs.sikuli"
running SikuliX-IDE: -Xmx512M -Dapple.laf.useScreenMenuBar -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine
-jar /Applications/SikuliX-IDE.app/Contents/sikuli-ide.jar -r /Volumes/GraphicsXRaid/04 Elements/_AE_Scripts_Effects/scripts from Kevin/Index Comps From Projects/Suppress_AE_Dialogs.sikuli
[error] FileManager: Not a valid Sikuli script: /Volumes/GraphicsXRaid/04.sikuli
[error] Terminating SikuliX after a fatal error! Sorry, but it makes no sense to continue!
If you do not have any idea about the error cause or solution, run again
with a Debug level of 3. You might paste the output to the Q&A board.
TEST 2 (quoted and escaped path):
$ /Applications/SikuliX-IDE.app/Contents/runIDE -r "/Volumes/GraphicsXRaid/04\ Elements/_AE_Scripts_Effects/scripts\ from\ Kevin/Index\ Comps\ From\ Projects/Suppress_AE_Dialogs.sikuli"
running SikuliX-IDE: -Xmx512M -Dapple.laf.useScreenMenuBar -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine
-jar /Applications/SikuliX-IDE.app/Contents/sikuli-ide.jar -r /Volumes/GraphicsXRaid/04\ Elements/_AE_Scripts_Effects/scripts\ from\ Kevin/Index\ Comps\ From\ Projects/Suppress_AE_Dialogs.sikuli
[error] FileManager: Not a valid Sikuli script: /Volumes/GraphicsXRaid/04\.sikuli
[error] Terminating SikuliX after a fatal error! Sorry, but it makes no sense to continue!
If you do not have any idea about the error cause or solution, run again
with a Debug level of 3. You might paste the output to the Q&A board.
Typically I call my Sikuli from a shell script using escaped
characters:
/Volumes/GraphicsXRaid/04\ Elements/_AE_Scripts_Effects/scripts\ from\
Kevin/Index\ Comps\ From\ Projects/Suppress_AE_Dialogs.sikuli
But I just ran a quoted version of the escaped path (TEST 2) and also
got a similar output. BUT, this time I noticed what it's doing. The
output says:
[error] FileManager: Not a valid Sikuli script:
/Volumes/GraphicsXRaid/04\.sikuli
This is interesting because even though the space after the 04 in the
path name is escaped and the entire path is quoted, it's tried to
truncate my path name to "/Volumes/GraphicsXRaid/04\.sikuli" instead of
"/Volumes/GraphicsXRaid/04\ Elements/_AE_Scripts_Effects/scripts\ from\
Kevin/Index\ Comps\ From\ Projects/Suppress_AE_Dialogs.sikuli"
I just moved my script to another test directory without a leading
number followed by a space and Sikuli is working normally. I can double
click and open the script file and it opens fine, as well as launch the
script from command line and it works as expected. Is the leading number
followed by a space crash a bug or am I missing something?
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.