sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #00656
[Bug 704437] Re: [request] AutoWaitTimeout should be a global setting used by all Regions unless set specific
Currently AutoWaitTimeout is in fact generally a Region specific
setting. when used without specifying a region object it addresses the
region SCREEN like all the other region methods.
I changed the title accordingly and fully support this request.
** Summary changed:
- must specifically set Region AutoWaitTimeout
+ [request] AutoWaitTimeout should be a global setting used by all Regions unless set specific
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/704437
Title:
[request] AutoWaitTimeout should be a global setting used by all
Regions unless set specific
Status in Sikuli:
New
Bug description:
This is an enhancement request bug - currently using Sikuli-X rc1 on
os x.
I'm using Regions to improve the locate speed of images and text.
I had this set at the beginning of my script: setAutoWaitTimeout(30)
However, when using find, or click in a region - I was getting
FindFailed, until I specifically set the AutoWaitTimeout for each
region:
SidebarRegion = Region(topx,topy,sidebar_width,app_height)
SidebarRegion.setAutoWaitTimeout(30)
mainwidth = int((vbarx-sidex)+vbarw)
MainViewRegion = Region(sidex,topy,mainwidth,app_height)
MainViewRegion.setAutoWaitTimeout(30)
It would be great if any region would use the default AutoWaitTimeout
if specified in the test, as opposed to having to set it for each
region. If a timeout is set for a region, then it should be used.
References