The framework for Unit1.cpp is now in place. OK, here are the objects and the events we need to handle: If you follow this scheme, Object Inspector will create and automatically name the event handlers to the same name used in our examples. Go to the event tab sheet in Object Inspector.ĭouble-click the blank space next to the event name. The easiest way to create events handlers is as follows:
Using the Object Inspector again, create event handlers for the following events. You should now have two Unit files: Unit1.cpp for Form1 activity and Unit2.cpp for the thread. Next, under the File | New menu, add a Thread Object. Using the Object Inspector, set Memo1 properties as follows: Obviously, you’ll want to add these and other elements to a fully functioning program.įire up BCB and start a New Project. There are no menus or other features to distract us from focusing on the serial comm aspect of the program. It will consist of a Form with a Memo object (for text I/O) and a Thread object that handles incoming serial data. In the example that follows we’re going to write a bare-bones program to do serial communication. You can also download the source code in BCBComm.zip.
If you’re already familiar with using BCB to develop Windows programs, the example code should be plenty to get you going. The purpose of this site is to spare you hardship of my early efforts and get you up and running with your Win9x/NT serial comm programming as quickly as possible. Borland’s C++ Builder has done a lot to help make Win95 programming easier and, once you know the tricks, the serial communications stuff is pretty easy, too. Yet, everything I knew seemed upside-down in the message-driven-callback world of Windows.Īfter spending lots of money on books and seemingly endless effort, I have finally gotten enough of a handle on Win95 and serial comm programming to write something usable in this environment.
Interrupt driven serial comm, DMA transfer serial comm, TSR serial comm, C, assembler, various processors…you name it, it had written it. It was particularly frustrating because I had, over the years, written so much stuff (including lots of serial comm software) for the DOS environment and numerous embedded applications. I, like many programmers, was hit with the double-whammy of having to learn Windows programming and Win95 serial comm programming at the same time. November wish this site had been around when I was trying to figure out how to make serial communications work in Windows95.
0 kommentar(er)
