Article View: borland.public.cppbuilder.nativeapi
Article #10266Re: Problem with WaitCommEvent in thread
From: Remy Lebeau (TeamB)
Date: Tue, 11 May 2004 16:45
Date: Tue, 11 May 2004 16:45
17 lines
1446 bytes
1446 bytes
"Martin Nijhoff" <dont@mail.me> wrote in message
news:40a0ce04@newsgroups.borland.com...
> Can you elaborate on that?
I suggest you read the following article for detailed explanations on the
proper use of a serial port:
Serial Communications in Win32
http://msdn.microsoft.com/library/en-us/dnfiles/html/msdn_serial.asp
The section on "Communications Events" explans why your application can be
blocked when you use non-overlaped operations across threads.
Gambit
Technical Details
Message-ID:
<40a10468$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!controlnews3.google.com!news1.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<40a092fd$1@newsgroups.borland.com> <40a0b26b@newsgroups.borland.com> <40a0ce04@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10cc67,4298e6c7d8d30497 X-Google-Attributes: gid10cc67,public From: "Remy Lebeau \(TeamB\)" <gambit47.no.spam@no.spam.yahoo.com> Newsgroups: borland.public.cppbuilder.nativeapi References: <40a092fd$1@newsgroups.borland.com> <40a0b26b@newsgroups.borland.com> <40a0ce04@newsgroups.borland.com> Subject: Re: Problem with WaitCommEvent in thread Date: Tue, 11 May 2004 09:45:22 -0700 Lines: 19 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 NNTP-Posting-Host: 67.22.138.253 Message-ID: <40a10468$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1084294248 67.22.138.253 (11 May 2004 09:50:48 -0700) Path: arc1-ca.pugleaf.net!controlnews3.google.com!news1.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail