> Not really - the binary functions are better for binary that > YOU control rather than that the operating system controls. > For example, a piece of binary that represents a code > sequence in your program (code as in cipher, not > programming). Since you control the size of that, it's ideal > for the binary storage. But since LOGFONT depends on compiled > header files and libraries in use by the OS - not so useful. > > Not that I'm suggesting you did anything wrong - just that > you have to be prepared for pitfalls such as this when you > aren't in full control of what you're storing.
I see. But question: The dialogue creates the logfont and writes it to reg. Another dialogue reads that logfont from the reg. Surely the logfont will be the same size? The system wrote it, the system reads it? No? This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding. _______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
