![]() If that's not the problem, I tested this simple script side-by-side with Window Spy (the version distributed with AutoHotkey) and the color values always matched exactly. ![]() MouseMove, %X%, %Y%, 1 Restore the original positionĬlipboard = %clipboard%`nX%X% Y%Y% Color = %color% SetFormat, integer, hex Report it in hex so that you can see the blue-green-red compoents more easily. Sleep, 50 Might need time to make it reliable. good for testing if a pixel is out of the current clipping region as it then. this will return a 32-bit value (Long) of the Pixel Color (RGB). ![]() Long, ByVal x As Long, ByVal y As Long) As Long. Move the cursor out of the way so that it doesn't block the pixel we want. Carl, Yes I dose ) Look up: Public Declare Function GetPixel Lib 'gdi32' Alias 'GetPixel' (ByVal hdc As. If you think that could be the problem, you could try a hotkey such as the following to retrieve the pixel color currently under the cursor: This tends to happen with non-standard cursors or in some types of games. It might have something to do with Window Spy misreporting the color due to the mouse cursor blocking the pixel you want.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |