AfxWndProc hook
-
Hi everyone ! Well, I have heard that the MFC runtime used a hook to dynamically link a component to its window procedure. I know that it's the best way to do it, but Microsoft itself advises the developers to use hooks in their applications only for debugging purposes, because it dramatically slows the programs down... What about MFC programs, are they much slower than their raw API equivalents ? Thanks in advance, Mark
-
Hi everyone ! Well, I have heard that the MFC runtime used a hook to dynamically link a component to its window procedure. I know that it's the best way to do it, but Microsoft itself advises the developers to use hooks in their applications only for debugging purposes, because it dramatically slows the programs down... What about MFC programs, are they much slower than their raw API equivalents ? Thanks in advance, Mark
Well, as far as I know that MFC uses window subclassing to override the default WndProc. Hooking is usually used to install the MFC WndProc to the created window. I dont know what hooks exaclty, but definitely not WH_CALLWNDPROC hook or anything like it, which involve notification of frequent events. Usually WH_CBT is used, which can notify the hooking application about creation of windows. Another thing, there is a difference of local hooking used in this process and global hooking in which the hook is installed over the whole system. To sum up, the hooking is used just to initiate subclassing and it's local to the process. Subclassing doesnt degrade performance (actually it is done using APIs). So if there existed a degreade on performance of MFC application I think hooking wont be the reason. Am saying this with accordance to my knowledge, hope if there is anything wrong someone would correct it
-
Hi everyone ! Well, I have heard that the MFC runtime used a hook to dynamically link a component to its window procedure. I know that it's the best way to do it, but Microsoft itself advises the developers to use hooks in their applications only for debugging purposes, because it dramatically slows the programs down... What about MFC programs, are they much slower than their raw API equivalents ? Thanks in advance, Mark
The hook that MFC uses is only installed for the time it takes to create the window. Basically, MFC installs the hook, creates the window, and uninstalls the hook. The hook has basically no influence on the program or the system. Incidentally, it's a thread-specific hook, so it would not slow down the system anyway. Hope this helps,
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
Hi everyone ! Well, I have heard that the MFC runtime used a hook to dynamically link a component to its window procedure. I know that it's the best way to do it, but Microsoft itself advises the developers to use hooks in their applications only for debugging purposes, because it dramatically slows the programs down... What about MFC programs, are they much slower than their raw API equivalents ? Thanks in advance, Mark