Pixel functions should accept HWND

[Valik]

The following pixel functions should accept an HWND:
PixelCheckSum
PixelSearch
PixelGetColor

Adjust PixelCoordMode options:
0 - Removed, no automatic "active window" stuff.
1 - Default, unchanged. Absolute coordinates for the screen if no HWND supplied. Absolute coordinates relative to the window if an HWND is supplied.
2 - Only valid with an HWND, relative to the client area of the window.

This is a script breaking change for those using the "active window" functionality.

[hiyoal]

Thank you for this!! This is a really good idea and it would enable bot makers to increase their bot making abilities so that everything could be done using de-activated windows.

Hiyoal

[anonymous]

I think we can have a non breaking strategy with syntax like

1. Pixel...( [HWND,] ...)

or

2. Pixel...( ... [,HWND])

personnaly I suggest 1. but if AU3Check or AutoIt4SCite is in trouble with this syntax we can adopt 2.

[J-Paul Mesnage]

anonymous was me

[Valik]

Replying to anonymous:

I think we can have a non breaking strategy with syntax like

1. Pixel...( [HWND,] ...)

or

2. Pixel...( ... [,HWND])

personnaly I suggest 1. but if AU3Check or AutoIt4SCite is in trouble with this syntax we can adopt 2.

It'll be #2. I'm not going to start something with #1. I do not like "skip-able" parameters. They are too confusing. A particular argument should always take the same data-type and not try to auto-deduce context based on the data-type.

[J-Paul Mesnage]

Added in version: 3.2.11.2