Matthew

I just had a thought... not that I'm being lazy, but I've noticed a number of the spelling typos are in the tooltips. Does your IDE have spellchecking? Or is there a way to maybe load the tooltip (and perhaps any other UIX) text into a word-processor to highlight and fix spelling errors? I was thinking that might be a bit more efficient than someone activating each tooltip, taking screenshots or notes, then submitting to you. If it's not that easy, then I will post errors when I run across them....

Sorry, I didn't get any notice of your replies. Plus I've been waaay deep in development. Thanks for the open response. I'll post some typos for fixing soon...

Hello, I have been using RealTerm for several years, and it is VERY useful. Thank you! I think one easy "low-hanging fruit" to improve visual quality is to fix spelling errors in the UIX. There are quite a few. I do understand priorities, and fixing bugs is usually more important than perfect spelling. However, some of us are a little bit OCD, and good spelling makes the world seem much more orderly! ;) Is there any way I can contribute to help fix spelling errors? I would be happy to help, if possible....

I think you are confused bout TCP/IP comms Am I? Well since we're being brutally honest, perhaps I was indeed "confused", but not about TCP/IP comms. Rather, perhaps it was due to RealTerm's extremely busy UI with its many options all over the place, which can sometimes result in ambiguous or overlooked settings or combinations of settings. Also notable... I have tested many telnet clients currently available, and yours is the only one that uses "CR NUL" by default for EOL. All others use "CR LF"....

I think you are confused bout TCP/IP comms Am I? Well since we're being brutally honest, perhaps I was indeed "confused", but not about TCP/IP comms. Rather, perhaps it was due to RealTerm's extremely busy UI with its many options all over the place, which can sometimes result in ambiguous or overlooked settings or combinations of settings. Also notable... I have tested many telnet clients currently available, and yours is the only one that uses "CR NUL" by default for EOL. All others use "CR LF"....

Hello, You will not see the problem in the RealTerm display when connecting 2 instances of RealTerm server/client because RealTerm is (apparently) masking the problem. Sometimes we say about this, "It is drinking its own koolaide" ;-) The easiest way I found to demonstrate is to run 2 instances of RealTerm on separate hosts, one as TCP server and the other as TCP client. For example.... hostA : "server:5555" hostB : "<IP address of hostA>:5555". Now run Wireshark on hostA (or hostB, shouldn't matter)....

Hello, You will not see the problem in the RealTerm display when connecting 2 instances of RealTerm server/client because RealTerm is (apparently) masking the problem. Sometimes we say about this, "It is drinking its own koolaide" ;-) The easiest way I found to demonstrate is to run 2 instances of RealTerm on separate hosts, one as TCP server and the other as TCP client. For example.... hostA : "server:5555" hostB : "<IP address of hostA>:5555". Now run Wireshark on hostA (or hostB, shouldn't matter)....

Hello, You will not see the problem in the RealTerm display when connecting 2 instances of RealTerm server/client because RealTerm is (apparently) masking the problem. Sometimes we say about this, "It is drinking its own koolaide" ;-) The easiest way I found to demonstrate is to run 2 instances of RealTerm on separate hosts, one as TCP server and the other as TCP client. For example.... hostA : "server:5555" hostB : "<IP address of hostA>:5555". Now run Wireshark on hostA (or hostB, shouldn't matter)....