Writes formatted data to the specified buffer. Any arguments are converted and copied to the output buffer according to the corresponding format specification in the format string. The function appends a terminating null character to the characters it writes, but the return value does not include the terminating null character in its character count.
If the function succeeds, the return value is the number of characters stored in the output buffer, not counting the terminating null character.
If the function fails, the return value is less than the length of the expected output. To get extended error information, call GetLastError.
The format-control string contains format specifications that determine the output format for the arguments following the lpFmt parameter. Format specifications, discussed below, always begin with a percent sign (%). If a percent sign is followed by a character that has no meaning as a format field, the character is not formatted (for example, %% produces a single percent-sign character).
The format-control string is read from left to right. When the first format specification (if any) is encountered, it causes the value of the first argument after the format-control string to be converted and copied to the output buffer according to the format specification. The second format specification causes the second argument to be converted and copied, and so on. If there are more arguments than format specifications, the extra arguments are ignored. If there are not enough arguments for all of the format specifications, the results are undefined.
A format specification has the following form:
Each field is a single character or a number signifying a particular format option. The type characters that appear after the last optional format field determine whether the associated argument is interpreted as a character, a string, or a number. The simplest format specification contains only the percent sign and a type character (for example, %s). The optional fields control other aspects of the formatting. Following are the optional and required fields and their meanings.
Pad the output with blanks or zeros to the right to fill the field width, justifying output to the left. If this field is omitted, the output is padded to the left, justifying it to the right.
Prefix hexadecimal values with 0x (lowercase) or 0X (uppercase).
Pad the output value with zeros to fill the field width. If this field is omitted, the output value is padded with blank spaces.
Copy the specified minimum number of characters to the output buffer. The width field is a nonnegative integer. The width specification never causes a value to be truncated; if the number of characters in the output value is greater than the specified width, or if the width field is not present, all characters of the value are printed, subject to the precision specification.
For numbers, copy the specified minimum number of digits to the output buffer. If the number of digits in the argument is less than the specified precision, the output value is padded on the left with zeros. The value is not truncated when the number of digits exceeds the specified precision. If the specified precision is 0 or omitted entirely, or if the period (.) appears without a number following it, the precision is set to 1.
For strings, copy the specified maximum number of characters to the output buffer.
Output the corresponding argument as a character, a string, or a number. This field can be any of the following values.
Single character. This value is interpreted as type WCHAR if the calling application defines Unicode and as type __wchar_t otherwise.
Single character. This value is interpreted as type __wchar_t if the calling application defines Unicode and as type WCHAR otherwise.
Signed decimal integer. This value is equivalent to i.
Single character. The wsprintf function ignores character arguments with a numeric value of zero. This value is always interpreted as type __wchar_t, even when the calling application defines Unicode.
Signed short integer argument.
String. This value is always interpreted as type LPSTR, even when the calling application defines Unicode.
Unsigned short integer.
Signed decimal integer. This value is equivalent to d.
64-bit unsigned hexadecimal integer in lowercase or uppercase on 64-bit platforms, 32-bit unsigned hexadecimal integer in lowercase or uppercase on 32-bit platforms.
Single character. The wsprintf function ignores character arguments with a numeric value of zero. This value is always interpreted as type WCHAR, even when the calling application does not define Unicode.
Long signed integer. This value is equivalent to li.
Long signed integer. This value is equivalent to ld.
String. This value is always interpreted as type LPWSTR, even when the calling application does not define Unicode. This value is equivalent to ws.
Long unsigned integer.
Long unsigned hexadecimal integer in lowercase or uppercase.
Pointer. The address is printed using hexadecimal.
String. This value is interpreted as type LPWSTR when the calling application defines Unicode and as type LPSTR otherwise.
String. This value is interpreted as type LPSTR when the calling application defines Unicode and as type LPWSTR otherwise.
Unsigned integer argument.
Unsigned hexadecimal integer in lowercase or uppercase.
Note It is important to note that wsprintf uses the C calling convention (_cdecl), rather than the standard call (_stdcall) calling convention. As a result, it is the responsibility of the calling process to pop arguments off the stack, and arguments are pushed on the stack from right to left. In C-language modules, the C compiler performs this task.
To use buffers larger than 1024 bytes, use _snwprintf. For more information, see the documentation for the C run-time library.
Windows 2000 Professional [desktop apps only] Windows 2000 Server [desktop apps only]
The feedback system for this content will be changing soon. Old comments will not be carried over. If content within a comment thread is important to you, please save a copy. For more information on the upcoming change, we invite you to read our blog post.