Err SetTextCelFormatBuffer (TextCel *tCel, char *buffer, uint32 bufSize)
sprintf() for formatting. If there is no format buffer attached to the cel (the default), sprintf() is not invoked at render time.
If the bufSize parameter is zero, any buffer already in the cel is removed, and if the buffer was acquired internally, it is released. (DeleteTextCel() also automatically releases an internally acquired buffer.)
If the bufSize parameter is non-zero, a format buffer is attached to the cel. In this case, if the buffer parameter is NULL, a buffer of the specified size is dynamically allocated internally. If the buffer parameter is non-NULL, it is a pointer to a buffer that you have either dynamically allocated or a static buffer within your application. When you specify your own buffer, you are responsible for releasing it; the library internals will not attempt to release a buffer you provided via a non-NULL buffer parameter.
A format buffer must be large enough to hold the largest possible formatted string that you try to render. Internally, at rendering time, the printf-style format string and arguments you supply are passed to sprintf() for formatting. If the resulting string is larger than the format buffer, the Debugger window displays a message, but memory beyond the end of the buffer has already been corrupted at that point. (This is a typical limitation of sprintf() processing.)
Many text cels can share the same format buffer to save memory. The buffer is only used while text is being rendered into the cel. Once UpdateTextInCel() returns, the buffer is no longer in use by that cel, and can be used in formatting the contents of another cel. The only time it is not safe to use the same format buffer for multiple text cels is in a multithreaded application where more than one thread might be calling UpdateTextInCel() simultaneously.