*.inl files contain the definitions of inline member functions.
inlsplit turns a .inl file into the corresponding .cc and .h files, placing an include guard (#ifndef _HEADER_H...#endif) around the .h file. It can also optionally generate preprocessor directives in the output files to tell the C++ compiler what line it is on in the .inl file (for error messages).
Analyzing the source of CxImage library (ximawnd.cpp), it seems the HDC value is used to format and draw the text on a temporary in-memory bitmap, and then the image is copied from this bitmap to CxImage object.
It does not look much optimized for speed, and maybe you will have time to investigate some other approaches, like creating your own HBITMAP object, drawing on it, and then saving it to a file, for example using CImage class from ATL/MFC?
I am writing an application that generates documents and I wqould like to open them in Microsoft Word automatically. Does anyone have an idea how to launch Word with the relevant document from within my application?
Its more of an anti-datatype. When used by itself (e.g. as a return value for a function) it means there is nothing coming back. When used as a pointer (void*) it means it is pointing to an address in memory, but you either don't know what datatype it is, or don't care what type it is (that is, that you are just concerned with the bytes that start at that address, and not the actual datatype that is there).
If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week