>I then put your code in and ran it with Online logging on and got the
>following.
>
>s 0A , where lower case s was the last thing my code did and 0A was your
>line feed code.
>In addition on the Online screen I saw the CR take effect.
>
>In Summary
>The terminal program did not display any of these hex values with the
>exception of 0A on the main display or in the Hex log file. Therefore I
>thought they were not being sent. They are being sent but not displayed or
>logged in the file.
The current version (1.4.1) logs what appears on the screen to the log
file, so most non-printing chars don't log.
I'm working on a 1.5 that has a "hex" terminal emulation mode where it does
8 bytes per line, along with ascii dump.
ie,
61 74 0d 0d 0a 4f 4b 0d at___OK_
I should be posting the first public beta of that version this week. So for
that version, just pick hex as your terminal type and you'll see a hex dump
'live'.
Brian
_____________________________________________________________________
Mark/Space Softworks voice 408-293-7299
111 West Saint John, 3rd Floor fax 408-293-7298
San Jose, CA 95113 <http://www.markspace.com>
PalmOS, Mac OS, Windows and Web Software & Solutions:
PageNOW! Wireless Messaging, PhoneWatcher Caller ID,
Fax Send and Receive for PalmOS
Online & Communicate terminal emulation and serial debugging
DataCord serial data cables for Handheld Devices
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
