Assertion From SendNotifyMessage
-
Why are you using
pParentWnd->GetSafeHwnd()to get your HWND? You should just useGetSafeHwnd()on its own. -
It gets to dlgcore by virtue of your call to
SendNotifyMessage, at which point it asserts because the handle you sent it is not valid. -
But the Window Handle is a Main or Mainframe Window I did a FindWindow api call To get the handle As the parent is a C console app and it did work once before I created the modless dialog box in the child process
-
But you are calling
pParentWnd->GetSafeHwnd()in a console app which makes no sense. What doespParentWndpoint to? -
Hi I am at work now however the only thing I can think of at this point is that I have to use DuplicateHandle to make the child main window accessible to the parent
No, you just need to find its handle by one of the enumerate functions, or get the child to pass it back in some way. A handle is just a pointer used to identify a Window so you can send messages to it. To be honest, I am not exactly clear about what you are trying to do beyond the basic SendMessage function.
-
No, you just need to find its handle by one of the enumerate functions, or get the child to pass it back in some way. A handle is just a pointer used to identify a Window so you can send messages to it. To be honest, I am not exactly clear about what you are trying to do beyond the basic SendMessage function.
-
"EnumThreadWindows" My questions in Windows is a threadID unique throughout Windows Thanksp
-
I would assume yes, since in the case of
EnumThreadWindows, the threadid is the only information Windows needs to return the information. -
Richard got the same assertion I believe this has to do with sharing window handles between threads I am going to use duplicate handle and see if that resolves the issue Thanks