When a script is run in TinyTERM for Windows, it’s compiled first. That compiled file has a maximum size of 98303 bytes (one less than hex value 18000). This limits the size of uncompiled script files as well, depending on the commands used. The limit needs to be removed.

For script files too large to compile, the workaround is to split it into multiple .cs files, then create an overarching script that uses the CompileFile() command to execute the smaller scripts in order.

CR 1053

When used in TN3270 emulation, the te.GetSelection() script command returns an empty string.

CR 1051

The Script_SessUp() function should be called automatically whenever a session opens. In 4.7.x, it only runs when first opening TinyTERM. Sessions opened afterward don’t run the callback function as they should.

CR 1029

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.

In TinyTERM’s Session Properties, program the right mouse button to paste with the %p custom string. Right-clicking in the TT window still produces the copy/paste menu. The left and middle mouse buttons accept custom strings. But the right button ignores them. The workaround is to script the TE_EMouseDown event.

CR 927, fixed in TinyTERM 4.65.4849

TinyTERM does support 28800 baud as a connection speed. You can set that with this script command:

te.baud = 28800;

But this option is not available in the user interface. Century Software has received a request to add it.

CR 887

Change the default background color in TinyTERM to anything other than the default blue. Then read the background color in CScript:

var test = te.GetBGColor(0);

test will always equal 0, regardless of the current background color.

CR 888

Set a background image in TinyTERM using CScript:

te.SetBackgroundImage("file.jpg",0);

The display does not change, though the command reports as running successfully.

CR 889

Open multiple sessions in a single TinyTERM window, at least three. Check the session number for each with this command:

te.displaynl(_str(IsSess(CSESS)));

They will be numbered in sequence left to right, starting with session 0.

Now close session 0, the one at the left. The remaining sessions will update their index numbers. The leftmost, which used to be 1, is now 0.

Click on the tab for session 0 to make it active. Then open another session. It opens as the leftmost session, pushing the active session’s tab to the right, but indexes to be the highest-numbered session. So the second session is 0, not 1.

Make that leftmost session active again, and open another session. It will open immediately to the right of the current session, leaving it at the far left. The new session will be the highest numbered. This makes the third tab session 0.

While this does not affect TinyTERM’s basic functionality, scripts that look for specific session numbers don’t find them in the correct place.

CR 878

When using CenTE.ocx in a custom application, pressing F1 in the control will normally bring up the help file. The file name auto-generated by the OCX is TECTRL.HLP, which does not exist. Documentation for the TE control is actually in the TinyTERM Programmers Reference Manual.

CR 857