Badly named constant in WindowsConstants.au3

[monoceres]

Not really a "bug" but I don't think that declaring $ERROR as const in WindowsConstants.au3 is a very good idea, since you then cannot use variables named $error, which is a very common name to name variables.
Just my 2 cents, it sure did cause me some headaches.

[monoceres]

Replying to monoceres:

Not really a "bug" but I don't think that declaring $ERROR as const in WindowsConstants.au3 is a very good idea, since you then cannot use variables named $error, which is a very common name to name variables.
Just my 2 cents, it sure did cause me some headaches.

I also found this, not very good constant names either:

Global Const $TRANSPARENT = 1
Global Const $OPAQUE = 2

[Valik]

Off the top of my head I'm not sure what $ERROR would be used for. However, the constants $TRANSPARENT and $OPAQUE really are the names of Windows API constants so I don't think we should change them.

[J-Paul Mesnage]

In fact this naming come from MSDN.
MS could have named it as the others ERRORREGION.
Perhaps we can change it as it use only when using _WinAPI_CombineRgn() or _WinAPI_GetWindowRgn()
The "problem" is the same for TRANSPARENT and OPAQUE in _WinAPI_Get/SetBkMode()

PS your headaches could have been little less when using Opt("MustDeclareVars",1)

[J-Paul Mesnage]

Fixed in version: 3.3.1.0