Think you know everything about "type-ahead"? The answer is no but soon it will be yes.

 

The original CSBAstat release (2003) assumed you were lazy data entry clerks. So it reacted to each keystroke in a name entry field to determine if sufficient characters had been entered to uniquely identify a name. This functionality was called "type-ahead". For example, typing characters to locate the player "Jones,Davy" who has a nickname of "Monkees":

 

j ... not unique (there's another player whose surname starts with J)

jo  ... not unique (another jo player)

joN ... yes that is enough characters to uniquely identify "Jones,Davy" as the player and the rest of  the full name is filled into the name entry field

 

Obviously it is scanning every player's name in the roster. But is also looking at every player that has a nickname. Consider:

 

M  ... not unique (there's another player whose surname or nickname starts with M)

Mo ... yes that is enough characters to uniquely identify "Jones,Davy" as the player and the rest of  the full name is filled into the name entry field

 

The upper/lower case doesn't matter. Any character is valid (eg punctuation, numbers, special characters). Just don't enter a blank character.

 

You can't be expected to remember how many characters are needed to uniquely identify each player. So you kept typing until you were told to stop. Do you remember the years when CSBAstat would automatically tab to the next grid cell and the superfluous characters were entered into the cell? By the way, that functionality was called "automatic tabbing" (or autotab for short). For example:

 

M ... not unique  (there's another player whose surname  or nickname starts with M)

Mo ... yes that is enough characters to uniquely Jones,Davy and the rest of  the full name is filled in and autotab occurs

Mon ... oh oh ... you're still typing ... 'n' is entered into the next cell

Monk ... oh oh ... you're still typing ...'k' is entered after the 'n'

 

Along came R8.0 (May 2021) and the functionality "automatic tab delay" (autotab delay) was introduced. The instant that uniqueness was found, all of the characters that you continued to type are thrown away. A miniature "stop sign" flashed on and off as long as you were typing. If enough seconds had passed since your latest keystroke, it decided that it is safe to autotab. And the "stop sign" disappeared.

 

The autotab delay defaults to 2.5 seconds. But if you are a slow typist, you might want to make it longer by copy/pasting this into your INI file ('n' is a decimal or integer bigger than 2.5):

 

[FCT_Form_AutomaticTabDelaySeconds]=n

 

Or if you are a super fast typist, you could make it smaller.