The local Braille keyboard is in force by default if the Braille keyboard configuration is simply switched on, or set up without the global option.

When the local Braille keyboard is in use, Braille key combinations are interpreted only when WTC is the active application. When you switch to another application, the keyboard behaviour reverts to standard character input.

You can use the Braille keyboard hotkey, Shift+WindowsKey+B by default, or the Braille menu item, to temporarily disable the Braille keyboard after it has been switched on or enabled at startup. This enables you to use standard key input temporarily if required, then enable Braille input again. Note, however, that whenever WTC is made the active application after another application has had the focus, Braille input is initially enabled, even if it was disabled when WTC went into the background. Of course, this is not the case if Braille input was never switched on or enabled in the first place, when standard input prevails all the time.

It should further be noted that pressing the Braille hotkey in local Braille keyboard mode when WTC is not the active application always reports that the Braille keyboard is enabled, even though it will not be active when you OK the dialogue. This is not a bug. When you are in another application, the Braille keyboard is disabled in local mode, so pressing the hotkey toggles it on, but when you OK the dialogue WTC is not the active application, so Braille input is disabled again and hence will report enabled next time you press the hotkey. The hotkey toggles Braille input on and off if WTC is active, as expected, there is no point in toggling it when WTC is not active for the local setting since it does not have any effect in remote situations.

Page url: http://wtcmanual.wintextware.com/index.html?bti_using_the_local_braille_keyboa.htm

Using the Local Braille Keyboard