BoBo wrote:Constructive critic:
a) while the "(file in) folder structure" setup is explicitly mentioned/advised here: https://autohotkey.com/boards/viewtopic ... 89#p168389
b) ... it's shown differently here: https://github.com/iseahound/Vis2
c) ... and it extracts from the zip the same way as described in b) not as in a)
Question, why not already provide the file you've advised to create manually (let's name it "my.ahk") ...
... within the zip-archive that gets extracted to Vis2's root folder, while Vis2.ahk itself will be hosted within the lib-folder (together with a local copy of an image and Gdip_All.ahk)
Based on that, the #Include-path within my.ahk would have been adjusted to point to Vis2.ahk in the lib-folder accordingly. All except the "capture text manually"-samples could be already part of my.ahk!
That would provide the user that "WOW"-effect right from scratch, and would decrease the number of support requests bc of errors made by the most error-prone part of scripting: me in front of the keyboard
This is good advice and I have implemented it.
Sadly, the current version of tesseract only runs on windows 10. (or windows 7 with the Microsoft Visual C++ 2015 and 2017 redistributable with x86/64-bit for each) The older version of tesseract I was using was targeting the 2008 C++ redistributable, and latest version will not compile on Visual Studio 2008. Rest assured, there are solutions but they will take time, as I will need to slowly learn many things. I will not forget Windows 7 users.