sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

Uuups, sorry - didn't realize it was for version 1.0.0

Yes, I purged this 2-arg version from the API.
In many cases, GUI actions (click, type, ...) need some wait afterwards. I want to implement a more general solution for this "wait after"

your suggested solution for dropAt() in the current situation is
correct.

Sorry for the inconvenience.

** 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

-- 
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 --- workaround

Status in Sikuli:
  Fix Committed

Bug description:
  *** 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

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