Re: mscomm in vc++ - parity error
- From: "Ali" <abdulrazaq@xxxxxxxxx>
- Date: 9 Dec 2006 22:46:33 -0800
Jim wrote:
"The Real Andy" Wrote:
mscomm32.ocx is a wrapper around the standard win32 libraries, if you
want complete control, then you are going to have to get away from
mscomm32.ocx. Hit codeproject for plenty of good examples.
Hi Andy,
Done that. Been there etc... There are several reasons why to use mscomm.ocx
the main one being that I've written loggers in the past and have classes
all ready to re-use, that use mscomm.
I was trying to find out how to do something in VC++ that can be done in VB
(VB uses Er.clear or something like that). Reason??? - Well, not only do I
have this new logger to write BUT I have a number of other loggers out there
with the same code. That is, bugged code!. If I get a real parity error my
logger is going to stop.
I guess if the answer is not out there then yes, I'll need to go a bit
closer to the bone. Code project, Code Guru etc. All have other serial
classes available - along with the associated bugs. I'd just 'rather' use
the tried and tested mscomm.ocx.
Thanks for your input
Jim
Snip:
There are several reasons why to use mscomm.ocx
the main one being that I've written loggers in the past and have classes
all ready to re-use, that use mscomm.
I was trying to find out how to do something in VC++ that can be done in VB
(VB uses Er.clear or something like that). Reason???
You are not that free to move if you stick to mscomm . You can write
your own wrapper for serial port and i would suggest to make it a
loadable module (dll) so it can be integrated to any application (VB ,
VC etc.). Have a look at
http://www.codeproject.com/system/cserialport.asp code and you can
convert this class to dll with little effort.
ali
.
- References:
- mscomm in vc++ - parity error
- From: Jim
- Re: mscomm in vc++ - parity error
- From: The Real Andy
- Re: mscomm in vc++ - parity error
- From: Jim
- mscomm in vc++ - parity error
- Prev by Date: Re: LIN and RS232
- Next by Date: Re: LIN and RS232
- Previous by thread: Re: mscomm in vc++ - parity error
- Next by thread: Intel 8096 ports 3 and 4 on romless parts
- Index(es):
Relevant Pages
|