sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #34645
[Bug 1190692] Re: [1.0] dropAt does not allow to specify delay after button release anymore --- workaround
** Changed in: sikuli
Status: Fix Committed => Won't Fix
** Summary changed:
- [1.0] dropAt does not allow to specify delay after button release anymore --- workaround
+ [1.0] dropAt does not allow to specify delay after button release anymore --- use wait() after
** Description changed:
*** workaround
dropAt(target)
wait(n)
-
- It is planned to have a more general solution for this "wait after
- action problem" in version 1.1.1
-----------------------------------------
Hi Raiman,
I just notice dropAt function only takes one argument right now, and I
didn't find anything in the release note. Did I miss anything? or it's
by design..
Thanks,
Frank
** Changed in: sikuli
Milestone: 1.1.0 => None
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1190692
Title:
[1.0] dropAt does not allow to specify delay after button release
anymore --- use wait() after
Status in Sikuli:
Won't Fix
Bug description:
*** workaround
dropAt(target)
wait(n)
-----------------------------------------
Hi Raiman,
I just notice dropAt function only takes one argument right now, and I
didn't find anything in the release note. Did I miss anything? or it's
by design..
Thanks,
Frank
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1190692/+subscriptions
References