diff --git a/sdk-api-src/content/winuser/nf-winuser-getwindowtextlengtha.md b/sdk-api-src/content/winuser/nf-winuser-getwindowtextlengtha.md index 3dc84456e11e..b87cf3fac7ee 100644 --- a/sdk-api-src/content/winuser/nf-winuser-getwindowtextlengtha.md +++ b/sdk-api-src/content/winuser/nf-winuser-getwindowtextlengtha.md @@ -73,22 +73,19 @@ A handle to the window or control. ## -returns +Type: int +If the function succeeds, the return value is the length, in characters, of the text. Under certain conditions, this value might be greater than the length of the text (see Remarks). -Type: Type: int - - -If the function succeeds, the return value is the length, in characters, of the text. Under certain conditions, this value may actually be greater than the length of the text. For more information, see the following Remarks section. - -If the window has no text, the return value is zero. To get extended error information, call GetLastError. - +If the window has no text, the return value is zero. +Function failure is indicated by a return value of zero and a GetLastError result that is nonzero. +> [!NOTE] +> This function does not clear the most recent error information. To determine success or failure, clear the most recent error information by calling SetLastError with 0, then call GetLastError. ## -remarks - - If the target window is owned by the current process, GetWindowTextLength causes a WM_GETTEXTLENGTH message to be sent to the specified window or control. Under certain conditions, the GetWindowTextLength function may return a value that is larger than the actual length of the text. This occurs with certain mixtures of ANSI and Unicode, and is due to the system allowing for the possible existence of double-byte character set (DBCS) characters within the text. The return value, however, will always be at least as large as the actual length of the text; you can thus always use it to guide buffer allocation. This behavior can occur when an application uses both ANSI functions and common dialogs, which use Unicode. It can also occur when an application uses the ANSI version of GetWindowTextLength with a window whose window procedure is Unicode, or the Unicode version of GetWindowTextLength with a window whose window procedure is ANSI. For more information on ANSI and ANSI functions, see Conventions for Function Prototypes. diff --git a/sdk-api-src/content/winuser/nf-winuser-getwindowtextlengthw.md b/sdk-api-src/content/winuser/nf-winuser-getwindowtextlengthw.md index 907663bd62fa..06f8d4220b76 100644 --- a/sdk-api-src/content/winuser/nf-winuser-getwindowtextlengthw.md +++ b/sdk-api-src/content/winuser/nf-winuser-getwindowtextlengthw.md @@ -73,22 +73,19 @@ A handle to the window or control. ## -returns +Type: int +If the function succeeds, the return value is the length, in characters, of the text. Under certain conditions, this value might be greater than the length of the text (see Remarks). -Type: Type: int - - -If the function succeeds, the return value is the length, in characters, of the text. Under certain conditions, this value may actually be greater than the length of the text. For more information, see the following Remarks section. - -If the window has no text, the return value is zero. To get extended error information, call GetLastError. - +If the window has no text, the return value is zero. +Function failure is indicated by a return value of zero and a GetLastError result that is nonzero. +> [!NOTE] +> This function does not clear the most recent error information. To determine success or failure, clear the most recent error information by calling SetLastError with 0, then call GetLastError. ## -remarks - - If the target window is owned by the current process, GetWindowTextLength causes a WM_GETTEXTLENGTH message to be sent to the specified window or control. Under certain conditions, the GetWindowTextLength function may return a value that is larger than the actual length of the text. This occurs with certain mixtures of ANSI and Unicode, and is due to the system allowing for the possible existence of double-byte character set (DBCS) characters within the text. The return value, however, will always be at least as large as the actual length of the text; you can thus always use it to guide buffer allocation. This behavior can occur when an application uses both ANSI functions and common dialogs, which use Unicode. It can also occur when an application uses the ANSI version of GetWindowTextLength with a window whose window procedure is Unicode, or the Unicode version of GetWindowTextLength with a window whose window procedure is ANSI. For more information on ANSI and ANSI functions, see Conventions for Function Prototypes.