When the host sets the number of columns in TinyTERM to 132, such as with the VMS command SET TERM/WID=132, the TinyTERM display changes appropriately. At some point afterward, the screen reverts to 80 columns. Neither the host nor the user needs to take any action to have this happen.

CR 917

TinyTERM for iPad 1.1 has the ability to change the text display area, based on whether or not the keyboard is visible. When the keyboard is brought back after being hidden, this sometimes causes data to scroll off the top of the screen.

This is due to the way TinyTERM deals with the changing number of lines and columns. It starts at the bottom left of the current display, then works up and to the right. Text that won’t fit in the reduced space is lost.

This is a compromise between the variable settings functionality and the amount of available space. It may not be the best way to handle the changes. Century Software welcomes suggestions on how this can be improved.

CR 916
CR 920

Century Software, Inc., has had a request to add support for the iPad VGA adapter to TinyTERM.

CR 911

Century Software has received a request to add support for Japanese kanji to TinyTERM for iPad.

CR 908

Century Software has received a request that TinyTERM for iPad automatically start the VPN when it’s launched. This would save a step in the connection setup process over VPNs.

CR 907

Century Software has received a request to add an automatic login capability to TinyTERM for iPad.

CR 906

Century Software has received a request for global color and encoding default in TinyTERM for iPad. This would allow a single set of colors, code pages, etc., to apply to all new connections after they are set.

CR 905, added in version 1.1.0

TinyTERM for iPad 1.0 does not include copy or paste capabilities. Century Software has had a request to add that functionality.

CR 904

When using Wyse50 or Wyse60 emulation in TinyTERM for iPad version 1.0, reverse text displays as a solid block instead. This is an initialization error in the text draw. It was corrected in TinyTERM version 1.1.0.