sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #22279
[Bug 1250634] Re: App.open() doesn't support starting directory
This is a long known request to pimp the App class (working directory,
parameters, ...)
Is on the list.
There are different workarounds (e.g. on Windows issue an appropriate
start command).
** Summary changed:
- App.open() doesn't support starting directory
+ [request] App.open() should support starting directory
** Changed in: sikuli
Status: New => In Progress
** Changed in: sikuli
Importance: Undecided => Medium
** Changed in: sikuli
Assignee: (unassigned) => RaiMan (raimund-hocke)
** Changed in: sikuli
Milestone: None => 1.1.0
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1250634
Title:
[request] App.open() should support starting directory
Status in Sikuli:
In Progress
Bug description:
App.open() (appopen()) only takes a single argument and it seems that
the option to provide a 'start in' directory isn't possible. Some apps
require that they are started in a particular directory to find
supporting files, but there doesn't seem to be a way to do this in
Sikuli.
Thanks
Sikuli 1.0.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1250634/+subscriptions
References