IsWindowVisible() may produce an error

[Enyium]

I was hesitant to commit the following text, which was based on tests, because it may sound like an unauthorized contract:

To be able to tell an absent WS_VISIBLE style apart from an error condition and retrieve extended error information, call SetLastError(ERROR_SUCCESS) in preparation to IsWindowVisible, and finally GetLastError.

(As Markdown)

To be able to tell an absent <b>WS_VISIBLE</b> style apart from an error condition and retrieve extended error information, call <b><a href="/windows/win32/api/errhandlingapi/nf-errhandlingapi-setlasterror">SetLastError(ERROR_SUCCESS)</a></b> in preparation to <b>IsWindowVisible</b>, and finally <b><a href="/windows/win32/api/errhandlingapi/nf-errhandlingapi-getlasterror">GetLastError</a></b>.

Or, a bit stronger:

To get extended error information, call GetLastError. To be able to tell an absent WS_VISIBLE style apart from an error condition, call SetLastError(ERROR_SUCCESS) in preparation to IsWindowVisible.

(As Markdown)

To get extended error information, call <b><a href="/windows/win32/api/errhandlingapi/nf-errhandlingapi-getlasterror">GetLastError</a></b>. To be able to tell an absent <b>WS_VISIBLE</b> style apart from an error condition, call <b><a href="/windows/win32/api/errhandlingapi/nf-errhandlingapi-setlasterror">SetLastError(ERROR_SUCCESS)</a></b> in preparation to <b>IsWindowVisible</b>.

Would it be okay to use one of those texts as the second paragraph under the "Return value" heading?

---

Tests I did on Windows 11 Home 24H2 (in another language, from memory):

SetLastError(ERROR_SUCCESS);
isVisible = IsWindowVisible((HWND)123);  // Invalid handle.
if (!isVisible) {
    DWORD lastError = GetLastError();
    // `lastError` is `ERROR_INVALID_WINDOW_HANDLE`.
}

///////////////////////////////////////

SetLastError(123);
isVisible = IsWindowVisible(validHwnd);
if (!isVisible) {
    DWORD lastError = GetLastError();
    // `lastError` is 123. So, preparation `SetLastError(ERROR_SUCCESS)` is needed.
}

[prmerger-automator]

@Enyium : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.