Re: [Sikuli-driver] [Question #254856]: sikuli-java 1.0.1 - The timeout used by exists method

2014-09-23 Thread Pathiyil
Question #254856 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254856

Pathiyil posted a new comment:
Ran a few tests. The machine has dual core 2.53 GHz processors and 12GB
RAM. The screens are 1920 X 1080. Each test was run a total of 4 times,
twice on each screen. In all the tests, the image being searched for was
not present in the screen.  The time was captured using java Date
objects. The numbers given are for each run.

With an image of size 47 X 47 pixels -

3666 msecs
1253 msecs
1113 msecs
1061 msecs

With an image of size 575 X 506 pixels -

2554 msecs
1883 msecs
1626 msecs
1651 msecs

With an image of size 1920 X 1080 pixels -

7215 msecs
6273 msecs
6107 msecs
6180 msecs

Just out of curiosity, replaced exists with a find having try/catch
around it. With an image of size 47 X 47 pixels -

3401 msecs
3270 msecs
3313 msecs
3303 msecs

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp


Re: [Sikuli-driver] [Question #254856]: [1.0.1] getting some seconds of find time with exists(img, 0) in cases where the image is not visible

2014-09-23 Thread RaiMan
Question #254856 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254856

Summary changed to:
[1.0.1] getting some seconds of find time with exists(img,0) in cases where the 
image is not visible

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp


Re: [Sikuli-driver] [Question #254856]: sikuli-java 1.0.1 - The timeout used by exists method

2014-09-23 Thread RaiMan
Question #254856 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254856

Status: Open = Answered

RaiMan proposed the following answer:
ok, that are the values, we have to live with currently (up to version
1.1.0) in case of exists-not-found.

On my Win8-64 i7/3.4 (1920x1200) I get similar values with version 1.1

In version 1.2 I will add some optimization by dispatching chunks of
search into different threads, to better use multicore systems.

In 1.1.0 I have added find profiling, that internally stores the elapsed times 
of the find ops with the Match and the search Region:
someMatch.getTime()
someRegion.getLastTime()

both return as long the duration in msecs of the last find op.

So this might make it a bit easier, if you are only interested in the elapsed 
time consumed by a find op 
Be aware: your last example: if not found, this is always the given wait time 
(usually slightly larger) 
(except exists(img,0), since this always returns after the first trial)

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp


Re: [Sikuli-driver] [Question #254856]: [1.0.1] exists(img, 0): getting some seconds of find time in cases where a larger image is not visible

2014-09-23 Thread RaiMan
Question #254856 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254856

Description changed to:
see comment #9
for some explanation
-

I am using sikuli-java 1.0.1 with JDK 1.7 on a Win7 box.

When I am calling screen.exists(imageName), it seems to be coming back
only after about 5 seconds. Tried making it exists(imageName, 0), but
that didn't make it return any faster. The same was the case with any
value between 0 - 5. For all of these the autoWaitTimeout was the
default value of 3.

Tried calling screen.exists(imageName) after calling
screen.setAutoWaitTimeout(0.1), but that didn't help either.

When I pass values of more than 5 for the seconds parameter (say 15),
then it seemed to take that much of time.

Is this behavior expected ?

Thanks.

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp


Re: [Sikuli-driver] [Question #254856]: [1.0.1] exists(img, 0): getting some seconds of find time in cases where a larger image is not visible

2014-09-23 Thread RaiMan
Question #254856 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254856

Summary changed to:
[1.0.1] exists(img,0): getting some seconds of find time in cases where a 
larger image is not visible

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp


Re: [Sikuli-driver] [Question #254856]: [1.0.1] exists(img, 0): getting some seconds of find time in cases where a larger image is not visible

2014-09-23 Thread RaiMan
Question #254856 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254856

RaiMan proposed the following answer:
BTW: this is my test script (version 1.1.0):

# some base image to start with
base = find(1411456264567.png)

#create a small image
m = base.getCenter().grow(50)
small = Pattern(capture(m)).exact()

# create a medium image
m1 = grow(m.getTopLeft(), 0, 0, 570, 500)
medium = Pattern(capture(m1)).exact()

#create the large image
m2 = Region(SCREEN)
large = Pattern(capture(m2)).exact()

# hide the stuff
if Settings.isWindows():
  switchApp(SourceTree)
else:
  switchApp(Finder)
wait(1)

# try to find
for i in range(2):
  exists(small, 0)
  print small:, getLastTime()
print m
for i in range(2):
  exists(medium, 0)
  print medium:, getLastTime()
print m1
for i in range(2):
  exists(large, 0)
  print large:, getLastTime()
print m2

… and I get this on my good old MacPro (Xeon 2,66 16GB)

small: 2223
small: 2180
R[40,39 50x50]@S(0)[0,0 1920x1200] E:Y, T:3,0

medium: 3318
medium: 3297
R[40,39 570x500]@S(0)[0,0 1920x1200] E:Y, T:3,0

large: 14796
large: 14856
R[0,0 1920x1200]@S(0)[0,0 1920x1200] E:Y, T:3,0

… so be happy with you machine ;-)

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp


Re: [Sikuli-driver] [Question #254856]: [1.0.1] exists(img, 0): getting some seconds of find time in cases where a larger image is not visible

2014-09-23 Thread Pathiyil
Question #254856 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254856

Status: Answered = Solved

Pathiyil confirmed that the question is solved:
Thanks for reviewing this and confirming the numbers.

My use case was to wait for the appearance of an image across all the
available screens till some max wait time. exists taking more than a
second threw my calculations off as far as number of iterations (using
the timeout between the checks as 1 / Settings.ObservedScanRate)

Altered my implementation to keep track of total elapsed time with a
more hard coded sleep time in between checks now.

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp


[Sikuli-driver] [Question #254915]: Unable to type URL because of shifting problem

2014-09-23 Thread Ryan
New question #254915 on Sikuli:
https://answers.launchpad.net/sikuli/+question/254915

Hello, I am trying to have Sikuli type a URL into a form, but have a problem 
because the shift key is not being activated.

In Sikuli: type(http://google.com;)

I want http://google.com to be inserted into the form. Instead, it is typing 
http;//google.com

I have tried several things including breaking the URL into pieces, saying 
first type(http) then adding either 
type(;, KeyModifier.SHIFT)
type(;, Key.SHIFT)

Unfortunately none of these are working. Any help/suggestions would be 
appreciated

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp


[Sikuli-driver] [Question #254918]: Running more than 10 scripts sequentially is failing.

2014-09-23 Thread Leochel
New question #254918 on Sikuli:
https://answers.launchpad.net/sikuli/+question/254918

Running more than 10 scripts sequentially is failing. I have a main script to 
run 36 scripts sequentially. Sikuli always fail when arrives to the lines 9 or 
10. If I run the scripts by separate do not fail.

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp


Re: [Sikuli-driver] [Question #254915]: Unable to type URL because of shifting problem

2014-09-23 Thread RaiMan
Question #254915 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254915

Status: Open = Answered

RaiMan proposed the following answer:
see faq 933
use paste() instead

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp


Re: [Sikuli-driver] [Question #254918]: Running more than 10 scripts sequentially is failing.

2014-09-23 Thread RaiMan
Question #254918 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254918

Status: Open = Needs information

RaiMan requested more information:
what version of Sikuli?
what system?
how do you run the scripts?
what errors do you get?
what are the symptoms?

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.

___
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help   : https://help.launchpad.net/ListHelp