ImageSearch is not reliable compare to python's pyautogui
Posted: 22 Dec 2021, 06:14
Hi all.
I trying to test AHK's ImageSearch to a function called locateOnScreen() from pyautogui
locateOnScreen() has a interesting parameter called "confidence", it's similar idea(maybe) to ImageSearch"s *n variation argument.
First of all, by using same image source, locateOnScreen() gives really reliable result, but with ImageSearch I will end up increasing the *n argument until it found result(although it's wrong)
~
So am I using it wrong ~ or there's a trick about using ImageSearch or maybe it's possible to implement a command like locateOnScreen()?
"pyautogui" (A python package based on pyscreeze (I guess pyscreeze based on CV2 and Pillow ~ and I sure Pillow used a lot of HDC stuff, which I think it's possible to implemet in AHK))
I trying to test AHK's ImageSearch to a function called locateOnScreen() from pyautogui
locateOnScreen() has a interesting parameter called "confidence", it's similar idea(maybe) to ImageSearch"s *n variation argument.
First of all, by using same image source, locateOnScreen() gives really reliable result, but with ImageSearch I will end up increasing the *n argument until it found result(although it's wrong)
~
So am I using it wrong ~ or there's a trick about using ImageSearch or maybe it's possible to implement a command like locateOnScreen()?
"pyautogui" (A python package based on pyscreeze (I guess pyscreeze based on CV2 and Pillow ~ and I sure Pillow used a lot of HDC stuff, which I think it's possible to implemet in AHK))