sikuli-driver team mailing list archive

[RaiMan <1890138@xxxxxxxxxxxxxxxxxx>]

use wait() instead.

This was a bad implementation in 1.x.

find() was always intended, to not wait for appearance, but search only
once.


** Changed in: sikuli
       Status: New => Won't Fix

** Changed in: sikuli
     Assignee: (unassigned) => RaiMan (raimund-hocke)

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

Title:
  Facing issue with Sikuli 2.0.4 version for find() function.

Status in Sikuli:
  Won't Fix

Bug description:
  Our objective is to be able to specify the timeout for the location of
  a bitmap.

  In early version of Sikuli i.e. 1.1.1 find() function internally calls
  autoWaitTimeout() which wait's for stipulated time like if we
  overrides the autoWaitTime by placing below code,

  sikuli_timeout = screen.getAutoWaitTimeout(); //it gives default time of Sikuli i.e. 3.0 sec
  screen.setAutoWaitTimeout(10); //Overriding autoWaitTimeout by setting 10.0 sec

  But in the latest version 2.0.4, find() is not calling the
  autoWaitTimeout due to which not able to override the default
  autoWaitTimeout. Please suggest how we can achieve this by some
  workaround.

  Sikuli version - 2.0.4
  Operating System - 64-bit Windows

  Please check the find() method of Region.class of 2.0.4 and 1.1.1 and
  do comparison.

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