Ask for help with programming questions about the use of MFC controls

mark it...

Sun Xin's tutorial seems to have it above。。。

Please study the font struct and the cfont class carefully, and check out the msdn

1.The release version will come with a lot of DLLs in the past, so it can be run on a machine without a programming environment. The debug version can only be said to be more formal in VS, but this version is more secure, especially in terms of memory, and is not prone to leakage problems.

2.Just that. db or. MDB file. The path relationship of the exe file is the same as that in the program.,In this case, it can still run normally.。

3.Yes, generally only as long as .

4.There are two types of installer creation: use VS or VC's built-in InstallShield for Microsoft VC; Use Installshield or other packaged software (e.g. nsis, etc.) (recommended).

5.If you want to use it in the program. dll and. lib file, just copy it to the target machine (or wrap it with the packaging software in question 4), you don't need to install it. net

For the difference between debug and release, you can check this out::

1. The release version is for distribution, the debug version is for debugging, and the debug version contains a lot of debugging information, so the generated exe is relatively large.

2. If win7 is used as a database server, you only need to indicate the IP address when the client connects to the database.

3. Yes. 4. For small programs, just copy the exe and related dlls directly, or package them into RAR

5. No.

Dynamically loaded DLLs have their own running space, which is separate from the running space of your program. Each space has a static instance.

If you can't understand it, Xiaoluyan thinks that DLL is also an application, and the memory space of the two applications is separated.

Usually, cwinapp in the exe has its own message pump, to ensure that the message pump is working normally, and the picture can also work normally. In the DLL, we generally do not open the message pump (except for another thread), and the DLL that does not open the message pump can also use the Qiaoyu cwinapp class, and it is also possible to change the name.

The display of modal dialogs depends on the message pump, which in turn depends on the thread. Calls in the same thread must be the same message pump. So not two modal dialogs are displayed at the same time.

Even if it is displayed at the same time, it must be that one of them can be operated and the other cannot be operated (the dialog is called in the dialog). Because it is modal, the dialog does not close, and the command to call the dialog will not be returned (there is no opportunity to call another dialog).

Operational UI can only be done on the main thread, which is Microsoft's rule.

Do you want to display two modal dialogs at the same time? If you want to display two modal dialogs at the same time and activate them at the same time, they are not"modality"dialog (you should consider making a non-modal dialog to make it look like a modal dialog).