Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Accessing Serial Port
Message
De
04/11/1999 08:25:04
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Contrôles ActiveX en VFP
Divers
Thread ID:
00286584
Message ID:
00286766
Vues:
15
>Craig,
>
>Mscomm clears its own buffer whenever .input is done. To see if the stream is ended or full, look at the .inbuffercount to see if it is stable (enough) or big enough to do the .input into your listbox.
>
>hth,
>Frank Camp
>

The alternative is to have the other end echo back the character stream and read it through the input buffer - that's a matter of how the other end handles the communication stream (it's often referred to as echoplex.) Check to see if you can have the other end echo back the stream, or alternatively, send some sort of ack at the end of a sucessful send.

>>I am attempting to utilize the Microsoft Communication Ole (MSCOMM32) in VFP 5.0. I am able to open the port and set the parameters and it appears to be working, but I don't know for sure. When I send a character stream to my computer's comm port and perform a receive request [i.e. frmMyForm.lstMyListBox.AddListItem(frmMyForm.oComm.input)] I never see the character stream that was sent. Preferably I want to automatically see (in a list box, window, screen, etc.) what was sent to the to the comm port every time a new stream is received.
>>
>>I would greatly appreciate any comments to point me in this direction including recommended periodicals to where I could do the necessary reasearch.
>>
>>Thanks In Advance,
>>Craig
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform