CreateFontIndirectconst

CreateFontIndirectconst is not a standard Windows API. It does not appear in official documentation or headers and is not recognized as a built-in function in the Windows GDI API. In practice, it may be encountered as a project-specific wrapper, a naming artifact, or a misnomer introduced by a developer aiming to emphasize const-correctness or to distinguish a wrapper around CreateFontIndirect from the original function.

The canonical Windows API is CreateFontIndirect, defined in Wingdi.h. It creates a logical font based on a LOGFONT structure and returns an HFONT handle, or NULL on failure. The LOGFONT describes attributes such as height, width, weight, italic, underline, strikeout, charset, and the face name. A font created by CreateFontIndirect uses device context metrics to map to the target device and must be deleted with DeleteObject when no longer needed to avoid resource leaks.

If you encounter a symbol named CreateFontIndirectconst, treat it as non-standard and inspect the codebase for its exact definition. It may be a wrapper that accepts a const LOGFONT* (or a const LOGFONT& in C++) and internally calls CreateFontIndirect, returning the resulting HFONT. Because there is no official API by that name, its behavior is implementation-specific and not portable across environments.

Best practices suggest using the standard CreateFontIndirect for portability and clarity. Always manage font object lifetimes with DeleteObject, and consider modern alternatives such as DirectWrite for high-fidelity text rendering, especially in new applications where GDI fonts are insufficient. If const-correctness is desired, implement it at the wrapper level rather than introducing an unsupported API name.