Not sure I follow, but what I just tried is the following:
Code: Select all
imageFile1 := "D:\\Documents\\AutoHotKey\\AHK v2\\images for imagesearch\keyboard trading off.png"
imageFile2 := "D:\\Documents\\AutoHotKey\\AHK v2\\images for imagesearch\keyboard trading on.png"
found1 := ImageSearch(&foundX, &foundY, x1, y1, x2, y2, "*162 " . imageFile1)
found2 := ImageSearch(&foundX, &foundY, x1, y1, x2, y2, "*162 " . imageFile2)
msgbox("Off " . found1)
msgbox("On " . found2)Wow, I never noticed that until I zoomed in close. Thanks for explaining how to resolve this issue.boiler wrote: ↑11 Apr 2024, 19:26If you zoom in on the images, it's very clear why you need so much variation to find them and what you should do about it. The vertical lines are produced by anti-aliasing, which is to place multiple pixels of different colors next to each other to fool the eye into thinking it's another color. That's how text and other images like these can look like they're sharper and have higher resolution than they actually have. You should color over all of those vertical lines (including the ones that are a very light yellow that you might not easily see at first) with a known color such as pure red (FF0000), and then use the *TransRed option. If you do that, it looks like you should be able to find each image with a variation of something like 5.
When coloring over the pixels of your reference images, you need to make sure to do it the right way. You need to use a tool like a "pencil" that paints in pure color pixels, not a "brush" that paints in blended edges. And you need to make sure the color you paint with is exactly what you think it is. If you select a red color, make sure it's FF0000 or make sure you know its exact value for use with the *Trans option.
Code: Select all
found1 := ImageSearch(&foundX, &foundY, x1, y1, x2, y2, "*160 *TransFF0000 " . imageFile1)Code: Select all
found2 := ImageSearch(&foundX, &foundY, x1, y1, x2, y2, "*220 *TransFF0000 " . imageFile2)Yes, once I figured out that WindowSpy shows colors, it was easy to see differences that my eyes could not see even with max zoom. MS Paint's line tool is distinct from the brush, but I guess when you go thicker than 1 pixel, it blends. This time I used the pencil, 1 pixel thickness (pencil also allows various thicknesses), along w/ WinSpy. I got both images down to only 2 colors each (I think).boiler wrote: ↑12 Apr 2024, 01:43Your new pixels are not all pure FF0000. Some are FE0000, FF0100, or FF0001. Any pixel that is not exactly FF0000 will not be skipped at all, so now you are searching for red pixels as well.
Using MS Paint is what I would suggest, but the method you described is suspect. You said you can specify a width. The width applies to brush tools, and I specifically said to use the pencil tool as that is the only one that will draw only in pure pixels of the specified color (and it always paints in a single pixel height/width). You should start again from the base images because if you try just painting over the current red ones, you might miss some since they are visually identical to FF0000.
Here are screenshots of the general area, with the keyboard button toggled on and off.
Sure, it's free with basic features, and that covers everything related to this particular issue. https://www.quantower.com/
Code: Select all
#Requires AutoHotkey v2.0
#SingleInstance Force
F5::msgbox GetWindowDpiAwarenessContextIgnoringInfoFlag(winExist("A")) ; #define DPI_AWARENESS_CONTEXT_UNAWARE ((DPI_AWARENESS_CONTEXT)-1)
GetWindowDpiAwarenessContextIgnoringInfoFlag(hWnd) {
AreDpiAwarenessContextsEqual(dpiContextA, dpiContextB) {
return dllCall("User32.dll\AreDpiAwarenessContextsEqual", "Ptr",dpiContextA, "Ptr",dpiContextB)
}
GetWindowDpiAwarenessContext(hWnd) {
return dllCall("User32.dll\GetWindowDpiAwarenessContext", "Ptr",hWnd, "Ptr")
}
if (dpiContextA:=getWindowDpiAwarenessContext(hWnd)) {
loop 5 {
dpiContextB:=-1*A_Index
if (areDpiAwarenessContextsEqual(dpiContextA,dpiContextB))
return dpiContextB
}
}
return false
}
Code: Select all
/*
The libraries used in this code, excluding Gdip, have not been shared anywhere, so it's not executable.
I plan to share them in the future, but I'm currently too busy to do so.
*/
#Requires AutoHotkey v1.1
#SingleInstance Force
#Include <FunctionGroup_Gdip_Ex-1.54.0-ahk1>
#Include <FunctionGroup_mmikeww.Gdip_All-1.54.0-ahk1>
#Include <FunctionGroup_MonitorExGet-1.0.0-ahk1>
pToken:=Gdip_Startup()
onExit("exitFunc")
exitFunc(_*) {
global pToken
Gdip_Shutdown(pToken)
}
F5::
if (hWnd:=winExist("A")) {
pBitmap:=Gdip_DpiBitmapFromHWND(hWnd) ; PrintWindow
hBitmap:=Gdip_CreateHBITMAPFromBitmap(pBitmap)
splashImage % "HBITMAP:" hBitmap
Gdip_DisposeImage(pBitmap)
}
return
Code: Select all
#Requires AutoHotkey v2.0
#SingleInstance Force
#Include <FunctionGroup_buliasz.Gdip_All-1.61.0-ahk2> ; #Include <Gdip_All> on your computer.
; AHKv2-Gdip
; 8960b875c4f1064865b51c72978d61e6648c0343
; https://github.com/buliasz/AHKv2-Gdip
pToken:=Gdip_Startup(), onExit((*)=>Gdip_Shutdown(pToken))
F5:: {
static DPI_AWARENESS_CONTEXT_UNAWARE:=-1
if !(hWnd:=winExist("A"))
return
if (getWindowDpiAwarenessContextIgnoringInfoFlag(hWnd)!==DPI_AWARENESS_CONTEXT_UNAWARE)
return
winGetPos(,, &width, &height, hWnd)
if (windowDpiScale:=dllCall("User32.dll\GetDpiForWindow", "Ptr",hwnd, "UInt")/A_ScreenDPI) ; In fact, I'm aware that there is a better API for this case, but since I'm still studying, I'll stick to the method I've been using so far for now.
width:=round(width*windowDpiScale), height:=round(height*windowDpiScale)
;------------------
hbm:=CreateDIBSection(Width, Height), hdc:=CreateCompatibleDC(), obm:=SelectObject(hdc, hbm)
PrintWindow(hwnd, hdc)
pBitmap:=Gdip_CreateBitmapFromHBITMAP(hbm)
SelectObject(hdc, obm), DeleteObject(hbm), DeleteDC(hdc)
Gdip_SaveBitmapToFile(pBitmap, sOutput:=A_ScriptDir "\ChartImage-" A_Now ".png")
Gdip_DisposeImage(pBitmap)
;------------------
if (fileExist(sOutput))
run(sOutput)
}
; ahk1.1 ahk2.0
GetWindowDpiAwarenessContextIgnoringInfoFlag(hWnd) {
AreDpiAwarenessContextsEqual(dpiContextA, dpiContextB) {
return dllCall("User32.dll\AreDpiAwarenessContextsEqual", "Ptr",dpiContextA, "Ptr",dpiContextB)
}
GetWindowDpiAwarenessContext(hWnd) {
return dllCall("User32.dll\GetWindowDpiAwarenessContext", "Ptr",hWnd, "Ptr")
}
if (dpiContextA:=getWindowDpiAwarenessContext(hWnd)) {
loop 5 {
dpiContextB:=-1*A_Index
if (areDpiAwarenessContextsEqual(dpiContextA,dpiContextB))
return dpiContextB
}
}
return false
}
Code: Select all
#Requires AutoHotkey v2.0
#SingleInstance Force
#Include <Class_iseahound.ImagePut-1.10.0-ahk2> ; #Include <ImagePut> on your computer.
; ImagePut
; 4bf78ee724527a150df9407d43e09940e1a378ff
; https://github.com/iseahound/ImagePut
; https://github.com/iseahound/ImagePut/blob/master/ImagePut.ahk
; https://github.com/iseahound/ImagePut/commits/master/ImagePut.ahk
; https://www.autohotkey.com/boards/viewtopic.php?t=76633
#Include <FunctionGroup_buliasz.Gdip_All-1.61.0-ahk2> ; #Include <Gdip_All> on your computer.
; AHKv2-Gdip
; 8960b875c4f1064865b51c72978d61e6648c0343
; https://github.com/buliasz/AHKv2-Gdip
pToken:=Gdip_Startup(), onExit((*)=>Gdip_Shutdown(pToken))
download("https://www.autohotkey.com/boards/download/file.php?id=25636", A_ScriptDir "\ChartImage_ToggleOff.png")
download("https://www.autohotkey.com/boards/download/file.php?id=25635", A_ScriptDir "\ChartImage_ToggleOn.png")
bufNeedleOff:=ImagePutBuffer(A_ScriptDir "\ChartImage_ToggleOff.png")
bufNeedleOn:=ImagePutBuffer(A_ScriptDir "\ChartImage_ToggleOn.png")
F5:: {
static DPI_AWARENESS_CONTEXT_UNAWARE:=-1
if !(hWnd:=winExist("A"))
return
if (getWindowDpiAwarenessContextIgnoringInfoFlag(hWnd)!==DPI_AWARENESS_CONTEXT_UNAWARE)
return
winGetPos(&winX, &winY, &winW, &winH, hWnd)
if (windowDpiScale:=dllCall("User32.dll\GetDpiForWindow", "Ptr",hwnd, "UInt")/A_ScreenDPI) ; In fact, I'm aware that there is a better API for this case, but since I'm still studying, I'll stick to the method I've been using so far for now.
winW:=round(winW*windowDpiScale), winH:=round(winH*windowDpiScale)
;------------------
hbm:=CreateDIBSection(winW, winH), hdc:=CreateCompatibleDC(), obm:=SelectObject(hdc, hbm)
PrintWindow(hwnd, hdc)
pHaystack:=Gdip_CreateBitmapFromHBITMAP(hbm)
SelectObject(hdc, obm), DeleteObject(hbm), DeleteDC(hdc)
bufHaystack:=ImagePutBuffer(pHaystack)
;------------------
state:=-1 ; Unknown
variation:=5 ; I thought a little variation wouldn't be necessary, but it is needed. I'm not sure why.
loop 1 {
if (xys:=bufHaystack.ImageSearchAll(bufNeedleOff,variation)) {
if (xys.length) {
state:=0 ; Off
break
}
}
if (xys:=bufHaystack.ImageSearchAll(bufNeedleOn,variation)) {
if (xys.length) {
state:=1 ; On
break
}
}
}
tooltip "state: " state
;------------------
Gdip_DisposeImage(pHaystack)
}
; ahk1.1 ahk2.0
GetWindowDpiAwarenessContextIgnoringInfoFlag(hWnd) {
AreDpiAwarenessContextsEqual(dpiContextA, dpiContextB) {
return dllCall("User32.dll\AreDpiAwarenessContextsEqual", "Ptr",dpiContextA, "Ptr",dpiContextB)
}
GetWindowDpiAwarenessContext(hWnd) {
return dllCall("User32.dll\GetWindowDpiAwarenessContext", "Ptr",hWnd, "Ptr")
}
if (dpiContextA:=getWindowDpiAwarenessContext(hWnd)) {
loop 5 {
dpiContextB:=-1*A_Index
if (areDpiAwarenessContextsEqual(dpiContextA,dpiContextB))
return dpiContextB
}
}
return false
}
Code: Select all
if !(hWnd:=winExist("Chart ahk_exe Starter.exe"))
return
Those are still not all pure red pixels. It's spiraling into something much more complicated than it needs to be. All that needs to happen is for this to be done correctly. It's easy to see they're not all FF0000 using the Window Spy tool.
I think what's happening is when the forum renders the images inline, it creates some distortion. When I see the images in my post, I can see that not all the red pixels are FF0000. But all the red pixels in the file are FF0000 - they have to be because I painted them with pencil using 1 pixel width. And I went over them just now.
Users browsing this forum: emp00, FalseShepard, mikeyww, vmech and 86 guests