not sure where to post this, found an error in documentation.

[xekon]

http://www.autoitscript.com/autoit3/docs/libfunctions/_ColorGetRGB.htm

#include <Color.au3>

_ColorGetRGB($nColor)

Success: an array of values in the range 0-255:

[0] Red component color

[1] Green component color

[2] Blue component color

Failure: set @error to 1

its actually BRG, not RGB

[0] Blue component color

[1] Green component color

[2] Red component color

here is how I have been making use of it:

$bgr = _ColorGetRGB("0x00"&Hex(_PixelGetColor_GetPixelRaw($vDC, $x, $y, $hDll),6))

[trancexx]

Out of curiosity, why do you have "0x00" and Hex() thingy?

[guinness]

If that is the case (I haven't checked) then this isn't a documentation error, because changing the return values would result in the function having to be renamed. I will now check.

[guinness]

Looks fine to me from the help file example.

[Melba23]

guinness,

And to me too:

#include <Color.au3>
$aRet = _ColorGetRGB(0xFF8000)
MsgBox(0, "Return", "Red: " & Hex($aRet[0], 2) & @CRLF & _
                    "Grn: " & Hex($aRet[1], 2) & @CRLF & _
                    "Blu: " & Hex($aRet[2], 2))

xekon,

Where does this _PixelGetColor_GetPixelRaw function come from? It is undoubtly that which is returning values which are confusing _ColorGetRGB.

M23

[xekon]

ahhh you are correct, it is because of the UDF it seems. (I use it cause it makes PixelGetcolor roughly 1,000 times faster when working on a large number of pixels like 100x100)

_PixelGetColor.au3

_PixelGetColor_GetPixelRaw

I should have investigated this farther.

[xekon]

Hey Thanks for that trancexx

"Out of curiosity, why do you have "0x00" and Hex() thingy?"

I have now simplified it to

$bgr = _ColorGetRGB(_PixelGetColor_GetPixelRaw($vDC, $x, $y, $hDll),6)

both ways give the same result, but this is less code

[guinness]

I should have investigated this farther.

It's always best to triple check when situations arise like this.