Copies a number of characters to consecutive cells of a console screen buffer, beginning at a specified location.
BOOL WINAPI WriteConsoleOutputCharacter( _In_ HANDLE hConsoleOutput, _In_ LPCTSTR lpCharacter, _In_ DWORD nLength, _In_ COORD dwWriteCoord, _Out_ LPDWORD lpNumberOfCharsWritten );
A handle to the console screen buffer. The handle must have the GENERIC_WRITE access right. For more information, see Console Buffer Security and Access Rights.
The characters to be written to the console screen buffer.
The number of characters to be written.
A COORD structure that specifies the character coordinates of the first cell in the console screen buffer to which characters will be written.
A pointer to a variable that receives the number of characters actually written.
If the function succeeds, the return value is nonzero.
If the function fails, the return value is zero. To get extended error information, call GetLastError.
If the number of characters to be written to extends beyond the end of the specified row in the console screen buffer, characters are written to the next row. If the number of characters to be written to extends beyond the end of the console screen buffer, characters are written up to the end of the console screen buffer.
The attribute values at the positions written to are not changed.
This function uses either Unicode characters or 8-bit characters from the console's current code page. The console's code page defaults initially to the system's OEM code page. To change the console's code page, use the SetConsoleCP or SetConsoleOutputCP functions, or use the chcp or mode con cp select= commands.
Minimum supported client
Windows 2000 Professional [desktop apps only]
Minimum supported server
Windows 2000 Server [desktop apps only]
|ConsoleApi2.h (via Wincon.h, include Windows.h)|
Unicode and ANSI names
WriteConsoleOutputCharacterW (Unicode) and WriteConsoleOutputCharacterA (ANSI)
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.