🚀 go-pugleaf

Thankkkkkkkkk UUUUU :))
  I had to keep work stopped for some days coz of those problems :( Well 
I'm a real novice with Indy, and all I learnt about it, it's thanks to 
Ur previous posts )

> DO NOT assign the ThreadMgr.ThreadClass property directly.
> TIdTCPServer handles that internally for you.  Assign only the
> TIdTCPServer's own ThreadClass property.  The ThreadMgr.ThreadClass is
> assigned automatically while the server is being activated.

Well the problem was that I set TIdTCPServer active at designe time, so 
ThreadMgr.ThreadClass was never assigned by itself!

> You must synchronize that with the main thread.  You cannot create MDI
> child windows outside of the main thread context.

Yes I managed to do that with a TidSync descendant class )

I got rid of all the try-catch blocks and used a custom descendant of 
TIdPeerThread, now Indy does all for me: allocating, deallocating .. so 
even if my clients disconnects, or my server shuts down, i get no more 
windows error messages(following to exeptions)!

Thank U very much again!
Stefano B