🚀 go-pugleaf

Hi
If you have written both the sending and receiving applications, which will 
mostly be the case, then do as I do and launch the sender from the receiver 
with CreateProcess(). Then you can arrange the sender to have a command line 
into which you can put the Windows handle of the receiver. This way there is 
no ambiguity about the handle. Also the sender can be closed when you close 
the receiver.

Just a suggestion

Ray
"Stefano Bonifazi" <stefboombastic@tele2.it> wrote in message 
news:4183708b@newsgroups.borland.com...
> Hi all!
> The problem arised with the previous thread about communication between 2
> applications of Mr. Christophe MINETTI:
> U need to use SendMessage to send WM_COPYDATA messages instead of
> PostMessage according to what MS stats!
> By using FindWindow U can get the handle of the Borland TApplication (
> FindWindow("TApplication","MyProjectName")), but it fails if I try to get
> the mainform handle instead (FindWindow("TForm1","Form1")).
> Stopping here I can only send the message to the "application window"...
> But the Application ->OnMessage event only allows me to handle message of
> the queue sent with PostMessage!!
> My workaround has been to use the EnumWindows functions to get the 
> mainform
> handle, then send the message to it and using the Form message handler (or
> by overriding the WndProc, or by using   BEGIN_MESSAGE_MAP ...
> END_MESSAGE_MAP(TForm); ) in the receiver application...
> My question are:
> 1)Is there a way to get SendMessage messages with the TApplication?
> 2)Is there a way to get the MainForm handle by using FindWindow?
>
> Thank U in advance!
> Stefano B.
>
>
>
>