Newsgroups : Borland : borland.public.delphi.internet.winsock : 2006 Apr : Re: TServerSocket.OnClientConnect is not executing.... why?
| Subject: | Re: TServerSocket.OnClientConnect is not executing.... why? |
| Posted by: | "Remy Lebeau (TeamB)" (no.spam@no.spam.com) |
| Date: | Fri, 28 Apr 2006 12:02:30 |
"John Klimek" <jklimek@gmail.com> wrote in message
news:44525a0f$1@newsgroups.borland.com...
> I'm not sure how I can call Application.ProcessMessages
Just call it.
> because my program is a console application
So? It can still have an active message queue. A console app is not a true
DOS app. It is a Win32 application without a GUI. It can do anything a GUI
app can do. TCustomWinSocket allocates a hidden HWND internally to receive
the socket messages.
> and thus no Application variable is created
Not true. If you are using the VCL, you do have an Application variable
available. The fact that you are using a console application does not
change that.
> or is my only option to use ThreadBlocking?
That is an option, and frankly, a better option for console apps in general.
Gambit
none