Problems passing data between dll and exe

scholar_zl

Should be the problem of passing data within the process?
I use a custom message in the dll
int cTxtLen = GetWindowTextLength (p-> hwnd);
Ranch
char * szWndName = new char [cTxtLen + 1];
Ranch
GetWindowText (p-> hwnd, szWndName, cTxtLen + 1);

SendMessage (g_hWnd, WM_DISPLAY_MSG, (WPARAM) szWndName, 0);

delete [] szWndName;

How to write the exe receiver?
I always write wrong.

moon_archer

Deleted by you.
New out in your exe, and then give the pointer and the length to the dll, dll judges the length, and writes in the content as appropriate.
exe received its delete after running out.

Or you can write like this, but don't delete here dll, dll provides a function, the parameter is a pointer, special delete.

In addition, you can delete in the exe, this is not recommended.

lklklk

Use files or use the registry for data transfer!
I do it all, it's not bad.

霜之哀愁

I think the first floor is wrong. . .
Sendmessage will not return until the exe is processed. If the WM_DISPLAY_MSG message is processed correctly in your exe, the following delete will work, so it will not be affected at all.
Just add a message response function in the main window of exe.

ON_MESSAGE(WM_DISPLAY_MSG, onDisplay)
........

You posted what you wrote, it should be something you wrote

ngchfc

Intercept the WM_DISPLAY_MSG message in the callback function of the g_hWnd window in the exe (do not make a mistake in the window).

In addition, the definition of WM_DISPLAY_MSG should not be duplicated with the system or existing. Use WM_USER+XXXX

scholar_zl

That's all right, I was taught the response message function like this:
BOOL CSurveillantView::onDisplay (WPARAM wparam, LPARAM lparam)
{
   AfxMessageBox (char*(wparam));
}
Please advise!

moon_archer

You directly comment out delete to see what the result is.

sunssjack

Passing data between processes
Shared memory pipeline...

scholar_zl

Comment out delete, windows prompts an error after running, and then terminate the program -_-!
I also encountered this error
The correction should be AfxMessageBox ((char*) wparam);

scholar_zl

Back to the 7th floor: I said that this should be in-process communication, right?