![]() you could bet dollars to donuts it was not going alone and was going to take at least one more program with it. An error in one program seldom meant only that program was 'going down'. ![]() While sharing memory was a little easier under Win/3, that was its real weakness - it was too easy to share. I don't think you, Gary, ever wrote for 16-bit Windows (PB/DLL 1.0 and 2.0), but for those of us who did, we all know that the both the process isolation and interprocess communication features of Win/32 were amongst the best new features. In the sending app, add a line after SendMessage like this: In the apps above, use SendMessage instead of PostMessage. Wait For Receiving App to Process Message: Pointer to a string variable in some kind of global memory? Some one will chime in here shortly with an answer, I know !. actually, I'm not sure yet how to pass a simple string. If you wanted to pass a decimal value, the wParam might contain all of the digits of interest, while lParam would contain the position of the decimal place. ![]() The receiving app can use the wParam and lParam values as simple Long values, or it might use them as an index for a pre-defined array of strings. ? "Message Received" + Str$(Cb.WParam) + Str$(Cb.LParam) ![]() GMsg = RegisterWindowMessage(MsgString) 'gets unique msg #ĭialog New Pixels, 0, "EXE #2 " + Str$(gMsg),300,300,200,200, %WS_OverlappedWindow To hDlg
0 Comments
Leave a Reply. |