> > 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 prov
> > 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
>
> 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 a th
ing a
callback.
> Now you've worried me a bit...
Sorry. You are now back to reality.
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Markus Humm" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Sunday, May 01, 2005 5:35 PM
S
[snip]
>>
>>The thing is that the code is in a dll, so application.processmessages
>>might not work here. Or does it? The timeout will be rather short anyhow
>>(ca. 50 ms) and I think i do it with GetTickCount, which should be
>>sufficient here and more easy to use than a at this place timer.
>>Or
PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Markus Humm" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Sunday, May 01, 2005 3:56 PM
Subject: Re: [twsocket] ReadLine
> Francois PIETTE schrieb:
> > As expressed in the source code,
Francois PIETTE schrieb:
> As expressed in the source code, ReadLine is deprecated. Anyway, it doesn't
> fit correctly with UDP protocol which is datagram oriented. Using "lines"
> with such protocol is strange.
>
>
>>Now I have the problem that at one place in the program I need
>>synchronus com
.overbyte.be
- Original Message -
From: "Markus Humm" <[EMAIL PROTECTED]>
To:
Sent: Sunday, May 01, 2005 9:49 AM
Subject: [twsocket] ReadLine
> Hello,
>
> I'm using TWSocket for UDP communications, so far it works quite good.
> Now I have the problem that at
Hello,
I'm using TWSocket for UDP communications, so far it works quite good.
Now I have the problem that at one place in the program I need
synchronus communication. I send out one byte and if I receive the same
byte within some short timeout, I assume that the device I'm talking to
has a echo mo
12 matches
Mail list logo
