No TinyTERM ITX product has a user-driven clear screen capability at present. The host system must clear the screen. Century Software has received a request to add an option to clear the screen on demand.
All TinyTERM for iOS products support the creation of custom keyboard layouts. When creating a custom layout, the keyboard key at the beginning of a row sets the default height value for the entire row. As such, using the
keyHeight argument in the definition of the first key in a row changes the height for all subsequent keys. This causes display problems with the keyboard: either rows that are too short, or blank rows next to keys that are supposed to overlap the next row instead.
The workaround is to insert a thin blank key of standard height at the beginning of the row:
TinyTERM versions 4.61 (July 2009) and higher are fully supported on Windows 8. However, TinyTERM must run in the Desktop interface. It is not enabled for the Metro interface at this writing.
TinyTERM does not currently run on Windows RT. Century Software, Inc., plans to produce a version of TinyTERM for RT in the near future.
TinyTERM for Mac has no script language support. Century Software, Inc., has received a request to add that capability.
TinyTERM for Mac supports SSH and telnet connections. Century Software, Inc., has had a request to add RS232 (serial) communication capability.
TinyTERM Pro for iPhone includes the capability to print the screen or send transparent print jobs to email. When this is done on iOS 6, any custom keyboard selected in TinyTERM Pro is ignored. Instead, the standard iPhone keyboard displays no matter what keyboard changes are made. Closing and restarting TinyTERM Pro is the only way to fix the display. This does not affect iPads running iOS 6, only iPhones and iPod Touch devices.
Wyse50 emulation does not consistently display graphics characters correctly. In normal use this may not be noticed. Graphics-intensive host applications are likely to have display problems eventually, though.
The hardware keyboard should be mappable on OS X by putting a
keyboard.dat file into
~/Library/Application Support/TinyTERM-ITX. But doing so does not actually change the keyboard behavior. A similar problem affects TinyTERM for Linux.
When using TN3270 emulation in TinyTERM Plus 4.7.4, some SSL connections will fail. This is tied to the addition of the LU name to the TinyTERM status bar. Earlier versions of TinyTERM Plus do not have this but.
When using TN5250 emulation, select the IBM 3477-FC terminal subtype. TinyTERM will not connect, though it will show that it is attempting to connect.