Add _WinAPI_SetCheckMethod() and modify _WinAPI_Check()

[Yashied]

A lot of people "suffer" when using _WinAPI_... functions which contain a _WinAPI_Check(). In most cases there is no reason to "fatal" exit the program. For example, when using the _WinAPI_DestroyIcon(). I believe that users need to be able to disable this option, and offers a simple approach to solving this problem without rewriting _WinAPI_... functions and maintaining full compatibility with the previously written programs.

[Yashied]

The necessary variables and functions

[Valik]

Most, if not all of these errors are already removed in the next beta. In the future (before the next stable release, so sometime in the beta period) all non-fatal fatal errors are going to be removed from the language.

[Valik]

I'm not sure why you closed this ticket, JP. You are still using __WinAPI_Check() all over the place in the code. The function itself is still in the code. In other words, this ticket is not complete because my statement of "all non-fatal fatal errors are going to be removed from the language" isn't even remotely close to being true.

I'm re-opening this ticket until it's actually complete.

[anonymous]

This cuts both ways. On the one hand _WinAPI_Check() is not needed. The user is able to identify the error. On the other hand removal of this functions may lead to incompatibility in the "old programs" or to more serious mistakes.

[Valik]

Setting as blocking. This needs done before the next beta (I think it may be done now but I need to double check).

[Valik]

Removed in version: 3.3.1.2