This page is laid out for easy navigation via JAWS:
This script version is aimed at TeamTalk 4.6 and 5.x. The previous script version was for TeamTalk versions 4.2 through 4.5. These newer scripts should also work with those older TeamTalk versions but have not been tested against them.
Note: This script version ends support for JAWS 10.0 and older. Going forward, these scripts will support the latest update to JAWS 11.0 and newer JAWS versions only, due to significant changes in the JAWS scripting language introduced in JAWS 11. Those needing to run JAWS 10 or older may still use the older 4.2 script version with older TeamTalk versions or run newer TeamTalk versions without scripts.
Documentation of script usage and features can be viewed by typing Insert+F1 twice in quick succession from within TeamTalk while these scripts are running.
This script version is dynamic, meaning that updates to it will be made "in place." Newer revisions will replace older ones, and I will add change notes to this section as changes are made.
Here are the changes in version 4.6, most recent first. In JAWS, use the h or 3 keys to move through changes by release date, or Tab to jump straight to the download links.
SetRegViewcommand works, that caused the installer not to find any JAWS versions on 32-bit Windows.
This update adds support for JAWS 2018. There is also a minor possible Braille speed increase.
This revision streamlines support for the latest TeamTalk 5.1 releases that speak chat messages on arrival natively and include proper names for more on-screen controls, such as volumes. As such, support for older TeamTalk versions is reduced in this revision.
There are also fixes for the commands for cycling among TeamTalk windows (Ctrl+` and Ctrl+Shift+`):
This revision fixes installer and compilation issues:
Chat timestamps always speak on Alt+NumPad5 regardless of verbosity settings, to provide a quick way to check the timestamp on a particular message.
Attempted to fix the problem of Ctrl+Shift+S occasionally saying nothing when multiple instances of TeamTalk are open at the same time.
The main change in this revision is that the installer works in JAWS 17 public beta 2. The change is necessary because of a change in script compiler flags between public betas 1 and 2 of JAWS 17.
This revision includes installer fixes only and supports JAWS 17 public beta.
Announcement of status information like who is sending sound, who is idle or online, etc., during navigation through the channel tree should be greatly improved on Windows 8/8.1 machines and high-DPI laptops under JAWS 15 and later. This enhancement may also apply on JAWS 14 but will not apply on older JAWS versions and has not been tested in JAWS 14 or older. These announcements may still fail to be completely accurate from time to time due to scrolling problems. In sufficiently new versions of TeamTalk 5, the new native Ctrl+G command will announce some of this information as well. (At this writing, Ctrl+G is only available in a beta TeamTalk 5 client.)
Anyone who sometimes found Ctrl+Shift+S silent should find this no longer to occur.
The standard JAWS Ctrl+JAWSKey+V command for reporting the current application version now reports the full correct version number.
The special code for making Ctrl+Left and Ctrl+Right navigate by word in a channel chat window is removed, because it actually worsened the behavior of these commands under recent JAWS versions.
The installer changed in this script version, with the following benefits:
This revision lets Ctrl+Alt+Left/Right raise and
lower voice volumes in TeamTalk 5 rather than saying "Not in a table"
and doing nothing.
This update also allows mostly silent installation via a
installer command-line option, and completely silent installation via
TeamTalk 5 (alpha, at this writing) should work with these scripts. As part of this, script files have been renamed. Anyone installing the scripts manually, without running the installer, must edit ConfigNames.ini in the JAWS user folder to link TeamTalk to the renamed file set. The following should work:
Chat commands' no longer miss the first entry in a channel chat window. (This bug may never have gone public.)
Blank participant names with no flags (like "Sending") in the channel tree no longer get replaced by the next tree item. This was happening on at least some Windows 8.1 machines with high-resolution displays.
TeamTalk window switching (Ctrl+`) works even when a subdialog, like a volume control, is open over a TeamTalk main window.
When typed in a TeamTalk main window (as opposed to a private chat window)
or in a dialog descended from one, such as a volume dialog,
SayWindowTitle command (Ins+T) includes the
server name before the actual main window name.
This is useful when multiple TeamTalk instances are running at the
same time, because it helps identify which is which.
When a message arrives in a TeamTalk channel message window for a TeamTalk instance with an empty channel tree, which generally means there is no fully active server connection, and that TeamTalk instance is not in focus, the server name on that window's status line is used to identify the window to which the message is sent. This situation often happens when a non-current TeamTalk instance's connection breaks due to Internet issues and begins placing messages about retries into its channel message window. This fix makes it easier, when multiple TeamTalks are running, to figure out which one's connection is breaking.
SayLine command (Insert+Up) twice
quickly should now spell the current line as it does in most
Radio buttons no longer announce count and position on up and down arrows, for consistency with behavior in other applications.