> > Defenitely not. Depending on the network traffic, you could easily have
> > something like one thousand messages per second in the queue.
> > The message loop must run full speed.
> >
> > As I said, you must either provide a callback to the DLL to call the
> > application's message pump, or hav
Francois Piette schrieb:
>
>
> Defenitely not. Depending on the network traffic, you could easily have
> something like one thousand
> messages per second in the queue. The message loop must run full speed.
>
> As I said, you must either provide a callback to the DLL to call the
> application'
> Hm, could that message pump be realised by a timer in the dll where the
> application.processmessages is called each onTimer event?
You can not use a TTimer since that uses windows messages and thus
needs the message loop. But you can use the windows SetTimer API with
a callback. I use such
- Original Message -
From: "Markus Humm" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Monday, May 02, 2005 6:29 AM
Subject: Re: [twsocket] ReadLine
You _always_ need a message pump. If the calling program doesn't provide
one, you must provide one and to have one without interferi
> 'GetMem(Buf, FBufSize);'
> where Buf := nil and FBufSize := 1460
> after that line, he gives me that error :s
That's normal Buf is nil and FBufSize is 1460. So GetMeme failed. This means
you run out of memory
or somewhere else you corrupted the data used by Delphi's memory allocator (for
examp
> > You _always_ need a message pump. If the calling program doesn't provide
> > one, you must provide one and to have one without interfering with the
> > calling DLL it is better to have all you stuff in a thread. Consider a
> > thread as a program within a program.
> > If you don't want to have
