Sikuli folder in root directory? --- not possible with rc3(930)

Asked by bengalih

This may be a bug, but perhaps I am missing something.

I am unable to get sikuli to run if the .sikuli folder is stored on the root of a drive.

For example:

C:\>java -jar "c:\Program Files (x86)\Sikuli X\sikuli-script.jar" c:\XBMCFlix-o-
mate.sikuli
[info] Sikuli vision engine loaded.
[info] Windows utilities loaded.
[info] VDictProxy loaded.
[error] Can't run this Sikuli script: c:\XBMCFlix-o-mate.sikuli
  File "<string>", line 1
    addModPath("c:\")
                    ^
SyntaxError: mismatched character '\n' expecting '"'

But, if I point it to the same .sikuli folder stored one level down in the directory structure, it works fine:

C:\>java -jar "c:\Program Files (x86)\Sikuli X\sikuli-script.jar" c:\v.1.2b\XBMC
Flix-o-mate.sikuli
[info] Sikuli vision engine loaded.
[info] Windows utilities loaded.
[info] VDictProxy loaded.
[info] add hotkey: CTRL+ALT+SHIFT O
[info] add hotkey: CTRL+ALT+SHIFT F
[info] add hotkey: CTRL+ALT+SHIFT N
[info] add hotkey: CTRL+ALT+SHIFT B
[info] add hotkey: CTRL+ALT+SHIFT T
[info] add hotkey: CTRL+ALT+SHIFT Q
[info] add hotkey: CTRL+ALT+SHIFT X

I realize it isn't recommended to put things on the root of your drive...but this was done by a user of my app. I first realized that my AutoIt wrapper script was appending a "\" when ascertaining the running directory of the root drive "C:\" as opposed to it returning no trailing slash for a subdir "C:\Subir". Once I accounted for that, I was able to launch into Sikuli fine....but it looks like Sikuli may have a similar interpretation problem when running off the root.

Please advise.

thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
j (j-the-k) said :
#1

I think this is a known bug, but I can't find the corresponding bug-entry on launchpad right now.

Revision history for this message
RaiMan (raimund-hocke) said :
#2

Yes it is a known bug. I linked it.

Revision history for this message
bengalih (bengalih) said :
#3

Thanks guys...I swear I did do a cursory search, but I must have overlooked it!

Luckily, I am using a wrapper script, so I will check in that to ensure not on a root drive, and alert the user until this is worked out.