sikuli-driver team mailing list archive

[RaiMan <sikulix@xxxxxxxxxxx>]

Thanks for the detailed explanation - appreciated and understood.

The solution would be to add the /D parameter to the issued start
command, which sets the starting directory.

To activate this setting, I will add

app.setWorkingDir("some directory")

which in turn will serve the start parameter /D.

To save typing of duplicate info the sequence:
app = new App("./runnable.exe").setWorkingDir("C:\Path\to")
app.open()
would expect the runnable in the given working dir and check that at time of open().

Without the ./ (or .\\) marker, the given program is found according to
the Windows rules.

Since I do not have access to a Window system (developing on Mac ;-)
during the week, you would do me a favour, if you could test the command

cmd /C start "" /B /D "C:\Path\to" "C:\Path\to\runnable.exe"

and confirm, that your program then is running in the working dir.

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

Title:
  [1.1.4] Windows: Working dir not set

Status in Sikuli:
  In Progress

Bug description:
  With an App object created with the path to an executable.

  When doing app.open().

  The working directory for the process is not set, hence causing some
  processes to be unable to run or function properly.

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