🚀 go-pugleaf

"Gene Buckle" <geneb@grumble.deltasoft.com> wrote in message 
news:48408535@newsgroups.borland.com...

> Whatever it does, does not contribute to the proper function of the 
> component. :)

Passing NULL versus 'this' to the constructor has no effect whatsoever on 
TIdTCPClient's ability to function.  All it does is establishes who is 
responsible for freeing the memory of the TIdTCPClient instance, nothing 
more.

> ShowMessage(TCPClient->Host) creates a blank dialog box.

Please show a more complete code snippet that actually compiles.  I'm 
guessing that you are not actually accessing the correct TIdTCPClient 
instance that you think you are.

> It would help if that kind of thing were documented..

Have you actually looked at Indy's documentation yet?

    http://www.indyproject.org/Sockets/Docs/index.EN.aspx

> After leaving IOHandler unassigned, it continues to throw exceptions:
> Simulator->TCPClient->IOHandler->WriteLn("foo!");
> ...results in an access violation.

All the more reason to suspect that you are accessing a different 
TIdTCPClient instance than you initially configured.

> Any suggestions as to how I can actualy make this work?  A C++
> example would be great.

It would be better if you would show your actual code.  Then someone can 
show you how to fix it.


Gambit