Dave

I understand and agree it's not a major issue, the only reason I raised it is because it would make implementing feature suggestion #61 a lot easier.

My before test: @Tattoo In [this line](https://github.com/eficode/robotframework-imagehorizonlibrary/blob/master/src/ImageHorizonLibrary/recognition/_recognize_images.py#L244) is there a reason for forcing `timeout` to an integer when time() returns a float to 6 decimal places? ``` stop_time = time()...

Never mind I see now why the limit at 1 sec, it takes ~800-900ms to identify the image, so it would never be able to be accurate down to 100ms...

Ok I wrapped int() around both time() calls and the timeout value, and like this it will pass even with a 0 sec timeout. I will submit this fix soon.

If the project owner likes this suggestion and would like i'd be happy to try implementing this feature.

The only reason for adding to `Does exist` was for consistency in behaviour, so that users would know any keyword that uses a reference image could have a timeout added....

My PR was tested on a mac with a Retina display running OSX 12.0.1, using tests/atest/calculator.robot from this project. I did need higher res images for the elements, I've attached...

I looked at the code for ImageHorizonLibrary.Take A Screenshot today, I think I can provide a fix for this.

From reading the [documentation](https://eficode.github.io/robotframework-imagehorizonlibrary/doc/ImageHorizonLibrary.html#Reference%20image%20names) is seems this has been implemented and documented already? is something missing? or should this issue be closed?

I don't have a travis-ci account, so I am wondering: - If this issue is resolved? - Was this issue preventing imagehorizonlibrary being tested on MacOS? if so could a...