Use AutoIt's image comparison features to automate things that otherwise require user interaction

Use AutoIt's image comparison features to automate things that otherwise 
require user interaction

Brief single paragraph overview:
Start using autoit image comparison features to find buttons, to figure out 
when the title bar changes, and use this in conjunction with better timing 
features. So if it on average takes 8 seconds to download an image. If it all 
the sudden starts taking 20 seconds. Then it maybe worthwhile to cut out after 
the average time is doubled rather than a static 1 minute. At this point when 
the avg time * 2 is encountered use the image features to look at the canvas. 
Does it show "100%" complete? Does it show the modified tool bar?" Etc. This 
can be used to make sure there's one tab and not two as well. 

What problem does this solve?
It speeds up execution. It helps make the tool be more independent of the user. 
This means it can be auto-keyed off by other scripts or programmatic conditions 
without having to worry about a user needing to be nearby to make sure the 
browser is in a sane state. Could help with issue 1.

Detailed request:
Possible solutions to implement this might come in the form of:
PixelSearch()
PixelChecksum()
PiselGetColor()
There are also several people who have worked out the basics of searching for 
images inside images 
(http://www.autoitscript.com/forum/topic/66545-find-bmp-in-another-bmp-imagesear
ch/)

Mockups (optional):
See images in issue 1 to get an idea of things that might be worth periodically 
looking for to check the sanity of the run.

Original issue reported on code.google.com by xtraeme...@gmail.com on 16 Nov 2012 at 8:48

Letractively / footnotereap

Use AutoIt's image comparison features to automate things that otherwise require user interaction #9