If you set the Destructive Back Space option in TinyTERM, the Backspace key should erase characters as it moves the cursor. This does not work in Wyse60, TN3270 or TN5250.

CR 743, Wyse60
CR 759, TN3270 and TN5250, fixed in TinyTERM Plus 4.7.0

The CScript command KeyLoad() doesn’t generate any debug errors when it runs. However, it doesn’t make any changes. Loading a new scheme with KeyLoad() doesn’t change the key mappings.

CR 719

Configure TinyTERM Plus for TN5250 or TN3270 emulation, then save the settings and exit. On your keyboard, turn NumLock on. When you start TinyTERM Plus, Num Lock shuts off. It also happens occasionally just by selecting either emulation.

CR 718

If Force Num Lock On is set in TinyTERM, some laptop keyboards will behave erratically. Other laptops ignore the setting. Typing on those works normally.

The problem stems from the dual nature of the typical laptop number pad. It tends to be a secondary function of the main keyboard, rather than a keypad of its own. With the laptop’s Num Lock off but the TinyTERM setting on, the function of any of the dual keys is not always predictable.

CR 705

PIXIL Thin Client currently includes keyboard layouts for US English, German, Italian, Italian 142 and French. Its time zones cover the Western Hemisphere. This will be expanded in future releases

CR 702, Swedish keyboard
CR 749, additional time zones

When you map a key to a string in TinyTERM, then come back to look at it later, it shows in the Value field as a series of numbers in angle brackets. For example, the word “key” displays as:

<619><613><633>

The Value Viewer line always shows the exact text. But that line has an absolute limit to how much it can display. It can’t be scrolled like the Value field can.

CR 656

In TinyTERM Plus’ Session Properties, set the terminal emulation to TN5250 and click the Apply button. Next, go to the Keyboard tab and click Edit. Click the Chart Open button. You get the 3270 keyboard chart. If you make changes and save the new mappings, it’s saved in the file keyboard.dat as a 3270 keyboard mapping.

This works properly in TinyTERM Plus 4.33 and earlier versions.

CR 650

Windows has a “standard keyboard buffer” feature which can be accessed programmatically. For example, the Visual Basic SendKeys function uses the buffer to pass information to other programs.

TinyTERM does not respond to input from the standard keyboard buffer. It has been reported that with a strict 16-bit implementation, TinyTERM will accept such input. However, that puts significant restrictions on the applications written to that standard.

CR 64

In the TN3270 and TN5250 emulations, the system keys — Print Screen, Scroll Lock and Break — can’t be mapped with Shift pressed. Century Software, Inc., has had a request to make these mappable. This has not been implemented thus far.

CR 629

The CScript command te.read() does not accept input from the numeric keypad when NumLock is on. When NumLock is off, te.read() outputs odd characters instead.

CR 616, fixed in TinyTERM 4.7.2, 15 March 2012