🚀 go-pugleaf

Hi Gambit

As per my last post I now use ICS and implemented some TCP messages instead. 
This works OK.
I finally got the API messages to work by filtering them according to the 
Windows they were sent (msg.hwnd), to make sure that I only read a message 
once.
The TTimer didn't do anything, it was just a test installation I used to try 
to understand the API messaging.

Rds
Marc



"Remy Lebeau (TeamB)" <no.spam@no.spam.com> schrieb im Newsbeitrag 
news:4726154f$3@newsgroups.borland.com...
>
> "Marc" <info@mawnet.com> wrote in message 
> news:4724b19d$1@newsgroups.borland.com...
>
>> I use HWND_BROADCAST because in future the
>> sender and receiver will be in two separate processes.
>
> That does not necessarily mean that HWND_BROADCAST is the best choice.  It 
> would be better if the sender knew ahead of time the HWND that the 
> receiver is actually using to receive messages with.
>
>> But when I create a second form, and place a TTimer component on it,
>> I receive the OutputDebugString twice. If I place two TTimer component
>> on it, I receive the OutputDebugString three times.
>
> What is your TTimer actually doing?
>
>> The second form is not event referenced in my first form.
>
> It doesn't have to be.
>
>> Curious enough this does not happen with a TButton component,
>> so it depends on the component I place on this second form.
>
> What component are you putting on the second form to reproduce the 
> problem?
>
>
> Gambit
>