Re: Serial comms and cotrolling the RTS line

Article View: borland.public.cppbuilder.nativeapi

Article #10286

Back to borland.public.cppbuilder.nativeapi Previous Next

#10286

From: evil
Date: Thu, 22 Apr 2004 07:10

14 lines
1142 bytes

On Tue, 20 Apr 2004 16:03:26 +0100, JoeBlack <no.one@no.where> revealed:
>     DWORD evt;
>     while (evt != EV_TXEMPTY)
>     {
>      WaitCommEvent(hComm,&evt,0);
>     }

If I were you I'd initialize evt properly to make sure it doesn't start out
as EV_TXEMPTY.
Does it return an error?

-- 

Acting stupid is often smart.

Technical Details

Message-ID: <slrnc8es04.qo.invalid@xs4all.nl>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!newshosting.com!nx02.iad01.newshosting.com!203.109.252.33.MISMATCH!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail

References: <40853bbf@newsgroups.borland.com>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10cc67,29200a53fdd311dc
X-Google-Attributes: gid10cc67,public
X-Google-ArrivalTime: 2004-04-22 00:27:45 PST
Newsgroups: borland.public.cppbuilder.nativeapi
From: evil <invalid@email.address>
Subject: Re: Serial comms and cotrolling the RTS line
References: <40853bbf@newsgroups.borland.com>
Message-ID: <slrnc8es04.qo.invalid@xs4all.nl>
User-Agent: slrn/0.9.7.4 (Win32)
NNTP-Posting-Host: 213.84.109.233
Date: 22 Apr 2004 00:10:57 -0700
X-Trace: newsgroups.borland.com 1082617857 213.84.109.233 (22 Apr 2004 00:10:57 -0700)
Lines: 15
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!newshosting.com!nx02.iad01.newshosting.com!203.109.252.33.MISMATCH!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail

Reply to Parent Message