TinyTERM ITX includes an optional function key button bar that can be displayed below the emulator window. These keys act the same as the F1-F12 keys on a physical terminal.

This is particularly helpful on the Mac, since the function keys can be configured for many other uses in OS X. So can other non-alphanumeric keys. Century Software has received a request to add keys to that button bar, such as the Insert and Delete keys.

CR 988

TinyTERM for iPad and TinyTERM ITX for iPhone both allow the user to build custom on-screen keyboards. The individual key rows are automatically centered when they are drawn. Century Software has received a request to allow the user to set a starting position for the keyboard, so that it can be left-justified.

CR 973

On iOS 3.x, TinyTERM for iPad versions 1.2.0-1.2.2 do not display the function keys when using the standard iPad keyboard. This happens whether or not an external keyboard is used. Custom keyboards in TinyTERM are not affected. This is related to the view clipping API, which changed in iOS 4.x.

Cr 951, fixed in TinyTERM for iPad 1.2.3

OS X uses function keys for a number of functions. So do most terminal emulations. Century Software, Inc. has had a request to add function key buttons to the TinyTERM ITX user interface, so that the keyboard function keys can be used for their standard Mac functions.

CR 941, added in TinyTERM ITX 1.0.6

TinyTERM for iPad uses a fixed amount of space for its custom keyboards, roughly the same screen area used by the standard iPad keyboard. Century Software, Inc., has had a request to make that amount of space adjustable. In particular, fewer keyboard rows would free up screen space for emulator display.

CR 938

When running TinyTERM on a Windows 7 PC and connecting via RS232 (Serial), the numeric keypad gives inconsistent output. At a shell prompt it works as designed. Inside applications, it fails intermittently. The Force NumLock On keyboard option has no effect on this behavior.

CR 936

Up to nine sessions can be opened in a single TinyTERM window. By default you must use the mouse to select one of these sessions, either from the Session menu, or by clicking a session tab.

There are two ways to configure a key to switch sessions. Both are done through the keyboard editor. To open that, go to TinyTERM’s Edit menu and select Settings. Select the Keyboard tab, then click the Edit button to bring up the keyboard map.

1. Rotate between sessions
To map a key that will switch to the next session in order, click the Chart Open button. This brings up the Drag & Drop Tables.

On the right of the table are five buttons labeled F, 1, 2, 3 and 4. Click the F button to bring up the Keyboard Meta Functions.

In the function list, use the mouse to grab the NEXTSESS item. Drag and drop it onto the desired key. When this key is pressed, it will switch to the next session in the list, rotating back to the first session if the last is currently active.

2. Go to a particular session
You can also map a key to go to a specific session. Sessions are numbered internally from 0 up to 8, with session 0 being the first one opened. For this example, we’ll map the Alt+function keys to switch between two open sessions.

In the map, click the Alt key. Then click F1. The Keyname field will change to AF1. Change the Action field to COMMAND. In the Value field, enter this string:

 SwitchSess(0,0);

Click the Set button to make this active. This maps the first session (number 0) to Alt+F1.

Next, click the F2 key. The Alt key should remain clicked, so the Keyname will be AF2. Again change the Action to COMMAND, and enter this in the Value field:

 SwitchSess(1,0);

Click the Set button again. This maps the second session (number 1) to Alt+F2. This can be extended to as many as nine keys.

Once you finish mapping the desired keys , click the OK button to close the keyboard map. Back in Session Properties, click the Save As button to give the new keyboard scheme a name.

If you’ve used Alt keys as in the above example, click the Use Alt keys in emulation box. Otherwise, the keys will be used by Windows instead of TinyTERM. In particular, Alt+F4 will close TinyTERM.

Whether you’ve used Alt keys or not, click the Apply button to make the changes permanent. Then click OK to close the Session Properties.

From TinyTERM’s File menu, select Save Session. That will complete your new key configuration.

TinyTERM for iPad includes a capsKey option for its keyboard, which can be used to create a “Caps Lock” key. There is no equivalent for the shiftTo option, which would allow the function or keypad keys to remain on screen until the shift key was pressed again.

A shiftLock option was added in TinyTERM version 1.2.0. Documentation was also added to the keyboard reference.

CR 925, added in version 1.2.0

TinyTERM for iPad originally did not include a Caps Lock key. That functionality was added in version 1.1.1.

There is a workaround for earlier versions. While using a custom keyboard layout, hold down the right Shift key, then hold the left Shift key for a second. This will lock the keyboard in Shift state. To turn off this shift lock, hide the keyboard, then restore it by tapping the screen once.

CR 915, added in version 1.1.1

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