I never know it is possbile to build parent-child relationship of two cross-process windows before. Now I know it is possible and it seems its behavior is like the local parent-child replationship. I implemented this a few days ago in Microsoft Word. That custom task pane is the parent of a user control whose child is another window from another process. Only an exception arose, the ribbon tabs cannot response to the mouse envents (mouse hover, mouse click), I have to send the WM_ACTIVATEAPP
to the active window (I cannot explain this phenomenon).
But the question is that does that mean I can use this mechanism with peace of mind? Are there some defects in the cross-process parent-child relationship? why no documents in Microsoft Doc? If I don't use this cross-process parent-child relationship windows, is there a better alternative? (for some reasons I asked in the previous posts, I have to implement two cross-process windows, which makes it possible to load two different versions dll
s).