How Much of WM_USER+X is used by MFC
-
Well, Using MFC, in a multithreaded environment, communication via SendMessage(...) is an essential. Trying to sculpt WDK Messages for my own purpose. Use WM_USER+x, Major Crash,turned out, WM_USER+x was already used by MFC42 in a control I used in my Dialog! has Anyone any idea what the range of messages are used or reserved by MFC in general, and what the Real Message range is, available to MFC developers.
++"#define WM_MFC_USERS 0xABXD1234
Or, something of that kind in some header somewhere. If this is the case, please let me know the Name and the value of the macro is. Regards :)
Bram van Kampen
-
Well, Using MFC, in a multithreaded environment, communication via SendMessage(...) is an essential. Trying to sculpt WDK Messages for my own purpose. Use WM_USER+x, Major Crash,turned out, WM_USER+x was already used by MFC42 in a control I used in my Dialog! has Anyone any idea what the range of messages are used or reserved by MFC in general, and what the Real Message range is, available to MFC developers.
++"#define WM_MFC_USERS 0xABXD1234
Or, something of that kind in some header somewhere. If this is the case, please let me know the Name and the value of the macro is. Regards :)
Bram van Kampen
WM_USERis obsolete. UseWM_APPinstead. Or better use registered messages. A good description about this topic can be found in the CodeProject article Message Management[^]. -
Well, Using MFC, in a multithreaded environment, communication via SendMessage(...) is an essential. Trying to sculpt WDK Messages for my own purpose. Use WM_USER+x, Major Crash,turned out, WM_USER+x was already used by MFC42 in a control I used in my Dialog! has Anyone any idea what the range of messages are used or reserved by MFC in general, and what the Real Message range is, available to MFC developers.
++"#define WM_MFC_USERS 0xABXD1234
Or, something of that kind in some header somewhere. If this is the case, please let me know the Name and the value of the macro is. Regards :)
Bram van Kampen
WM_USER+xshould only ever be used inside a single application, as it is free to use by everyone. Using it in a driver is almost bound to cause tears before bedtime. [edit] WM_USER (Windows)[^] and WM_APP (Windows)[^] list the rules. [/edit] -
WM_USER+xshould only ever be used inside a single application, as it is free to use by everyone. Using it in a driver is almost bound to cause tears before bedtime. [edit] WM_USER (Windows)[^] and WM_APP (Windows)[^] list the rules. [/edit]Thanks, I am aware of RegisterMessage(...) etc, but have always considered it as a canon to shoot a fly. It may be the better Idea for future, particularly after the nightmare I encounter now. Your idea of attaching a GUID is particularly fetching. WM_USER +X, It worked for me many a time in the past. I can now see the flaws Thanks, Bram. :)
Bram van Kampen
-
WM_USER+xshould only ever be used inside a single application, as it is free to use by everyone. Using it in a driver is almost bound to cause tears before bedtime. [edit] WM_USER (Windows)[^] and WM_APP (Windows)[^] list the rules. [/edit]Hi, Good to talk again. My header files do not provide a macro for WM_APP. Maybe you could let me know for future reference, if it is a single value. Also AOP has advised me to Register a Windows Message. Probably the way forward for the Future. Thanks for your contribution. Bram. :)
Bram van Kampen
-
Thanks, I am aware of RegisterMessage(...) etc, but have always considered it as a canon to shoot a fly. It may be the better Idea for future, particularly after the nightmare I encounter now. Your idea of attaching a GUID is particularly fetching. WM_USER +X, It worked for me many a time in the past. I can now see the flaws Thanks, Bram. :)
Bram van Kampen
-
It looks like a reply to my answer posted to yours inadvertently.
-
It looks like a reply to my answer posted to yours inadvertently.
-
Hi, Good to talk again. My header files do not provide a macro for WM_APP. Maybe you could let me know for future reference, if it is a single value. Also AOP has advised me to Register a Windows Message. Probably the way forward for the Future. Thanks for your contribution. Bram. :)
Bram van Kampen