DISCLAIMER: The following information concerns an out of date version of Window-Eyes. Program features and enhancements may not reflect the current state of Window-Eyes development. GW Micro may not be liable for any errors, inaccuracies, omissions, or out-of-date information contained herein. For information regarding the current version of Window-Eyes, please refer to the Latest Features page.

Window-Eyes: Performance, Reliability, and Stability
"Unleashing the power of your mind's eye."
©1995-2009 GW Micro, Inc. All Rights Reserved
E-Mail: support@gwmicro.com
Phone: 260-489-3671
Released: 6/26/2009

[Please note: The following information can also be found in the Window-Eyes Readme option, under the Help menu in the Window-Eyes Control Panel.]

Welcome to Window-Eyes 7.1

GW Micro is proud to offer Window-Eyes 7.1. Window-Eyes 7.1 builds on the success of previous versions, maintaining an expected high standard of stability, performance, reliability, and security, even as additional hardware and software platforms are supported. Support for 64-bit operating systems, Microsoft's upcoming Windows 7, and enhanced Braille and Scripting support are some of the main features that Window-Eyes 7.1 offers. You'll also notice quite a bit of fine-tuning, including better standard edit box support, and better access to menus, creating a richer, more accurate computing experience. Keep reading to learn more about Window-Eyes 7.1, and what it can do for you.

Keeping In Touch

Now that you have the power of Window-Eyes at your fingertips, why not join up with other Window-Eyes users on the GW-Info e-mail list? To subscribe, visit http://www.gwmicro.com/support/email_lists/, enter your email address in the email edit box, and select the Subscribe GW-Info button. Alternatively, you can send an e-mail message to listserv@gwmicro.com. Leave the subject blank, and type "join gw-info, your email address" in the body (without the quotes, but note that the comma is required). For example, "join gw-info, myemail@abc.com"

Regardless of the method you choose, you will receive a confirmation. Reply to that confirmation (with no modification) and you will become a member of the largest public network of Window-Eyes users, always eager and willing to answer any questions you may have. Although we encourage all users to help each other with questions and problems, you can take comfort in knowing that the GW-Info list is constantly monitored by GW Micro employees.

You may also contact us directly by using the contact information listed above. Thank You!

Window-Eyes is developed with you in mind. Please feel free to contact us regarding any questions, comments, or suggestions that you may have; we are anxious to hear from you. Now read on to learn more about your latest investment, and thank you for choosing Window-Eyes!
IMPORTANT INFORMATION

The following documentation consists of important information that you need to know before using this version of Window-Eyes.

1. You must already have an existing copy of Window-Eyes 7.0 or 7.01 installed before installing Window-Eyes 7.1. Retail versions (including non-copy protected versions inside the United States, and Dongle and Everlock copy protected versions outside the United States), Payment Plan, Evaluation, and Demonstration versions are supported.

2. Window-Eyes 7.1 is a FREE upgrade for all Window-Eyes 7.0/7.01 users. Window-Eyes 7.1 will not work on a version of Window-Eyes less than 7.0. If you are running a version of Window-Eyes less than 7.0, you will need to purchase an upgrade to Window-Eyes 7.1. Contact orders@gwmicro.com, or call 260-489-3671, for additional information.

3. Window-Eyes 7.1 supports both 32-bit and 64-bit operating systems (refer to the list of supported opreating systems below). If you are installing on a 64-bit operating system, you must contact orders@gwmicro.com (or via phone at 260-489-3671), and purchase a Window-Eyes 7.1 installation CD for $20 (assuming you own Window-Eyes 7.0/7.01. Older versions will require an additional upgrade cost).

This readme is divided up into various sections. The start of each major section will begin with two plus signs and the start of each minor section will begin with two minus signs. This means that you can search for ++ to move to the start of a major section, and -- to move to the start of a minor section. If you are reading the manual on a Windows PC using Notepad, we recommend maximizing the Notepad window with ALT-SPACE, then X. It is also a good idea to make sure that "word wrap" is enabled. This is usually found under the format menu of Notepad.

++New Features in Window-Eyes 7.1

Window-Eyes 7.1 introduces support for 64-bit versions of Windows Vista, Windows Server 2008, and Windows 7. 64-bit support is identical to 32-bit. In other words, all of the functionality, performance and stability you expect from Window-Eyes will exist regardless of the operating system you choose to use.

Window-Eyes 7.1 includes support for the latest, upcoming Microsoft operating system: Windows 7. Both 32-bit and 64-bit versions of Windows 7 are supported.

The following is a complete list of supported operating systems using Window-Eyes 7.1:

32-Bit:

* Windows 2000
* Windows 2000 Server
* Windows XP Home
* Windows XP Professional
* Windows XP Media Center
* Windows Server 2003
* Windows Vista Home Basic
* Windows Vista Home Premium
* Windows Vista Business
* Windows Vista Enterprise
* Windows Vista Ultimate
* Windows 7 Home Basic
* Windows 7 Home Premium
* Windows 7 Professional
* Windows 7 Enterprise
* Windows 7 Ultimate

64-Bit:

* Windows Vista Home Basic
* Windows Vista Home Premium
* Windows Vista Business
* Windows Vista Enterprise
* Windows Vista Ultimate
* Windows Server 2008
* Windows 7 Home Basic
* Windows 7 Home Premium
* Windows 7 Professional
* Windows 7 Enterprise
* Windows 7 Ultimate

All service packs and maintenance releases of the aforementioned operating systems are also supported.

Window-Eyes now provides support for Internet Explorer 8, and Thunderbird 3.

Thanks to our close relationship with Apple and their commitment to resolving accessibility issues, we continue to provide enhanced support for iTunes.

Window-Eyes now communicates directly with standard edit controls rather than relying on the OSM to retrieve text. This is an enormous improvement. As in Microsoft Word, Window-Eyes now boasts 100% text-accuracy 100% of the time in standard edit box controls.

We've completely re-designed the way that Window-Eyes speaks menus and menu items. Menu tracking should now be much more accurate in more applications than before.

We've increased processing power when using SAPI and Eloquence, which should eliminate any choppy or cut up speech. Note that this will not affect the built in Eloquence pauses. If you're using Windows Vista or Windows 7, you should make sure you have the absolute latest sound card drivers from your sound card manufacturer to help alleviate any software speech sluggishness.

The list box speed up that existed in 7.0 has been ported over to combo boxes, making them much faster.

When moving by character via the cursor, we now say, "Tab" when coming upon a tab. If we don't know how to speak something, we'll say, "Unicode blah" instead of speaking nothing.

Added a /? command line parameter to wineyes.exe which displays a message box containing all available command line options.

Added Status Window to the types of reclass possibilities in the Reclass dialog.

-- Scripting (General)

We have added the ability to check for, download, and install script updates from the Add Remove Packages dialog, complete with progress bars when checking and downloading. This means you can go to one place and check for updates for all your scripts at one time. This should make upgrading scripts much more intuitive for beginner users (and even some advanced users). Just select the new Check for Updates button in the Add or Remove Packages dialog. This brings up a new dialog that lists all of your outdated scripts, their version numbers, and the versions that are available from Script Central. You can then either select the ones you really want to update and activate the Update button or just activate the Update All button to update them all. The Show Package Details checkbox is used to indicate whether you want to see the package details if they exist for each script as they are installed. If a script has a license, you will be shown that no matter what. If there are no licenses and you have the checkbox unchecked then it will all happen silently.

The Package Manager dialog has been redesigned a bit. Localized Language is now the first combo box, allowing for quick adjustment of all the other language dependent controls in the dialog. Also, you can now include a Script Name that will be used whenever information about the package is displayed (such as the Add/Remove Package dialog, the Update Package dialogs, etc.). The Package Preview and Package License dialogs will also use the package display name (if provided).

The two list boxes in the package manager dialog that list package files and associations are now listviews. This makes it much easier to select items.

When the Package Manager dialog first opens, the Add Files button is the default button. When the Create Package button becomes enabled, it will be made the default button.

When script packages are created and/or extracted, any read-only attributes on the files involved are removed.

Script packages are now compatible with foreign language characters.

We removed the message in the Package Manager that prompted the package creator to enter package details. They're not required, so now we don't pester.

Added a new column to the Script Manager dialog called Name. Name is the friendly name of the script if it exists (specified with ClientInformation.ScriptName), otherwise, it's the script file name.

A restart button has been added to the script error dialog.

You can use the commandline parameter /useStatusColors to have the Script Manager dialog display the status column using colors. This visual enhancement indicates running scripts in green, stopped scripts in a shade of read, running with errors a different shade of green, and so on.

Clicking on the list view headers in the Script Manager now sorts the columns.

-- Scripting (Object Model)

Added the ability for scripts to create standard menus in custom XML dialogs. This means your dialogs can now have menu items like, "File, Edit, View, etc," providing users with a more intuitive, recognizable, and comfortable way to access script options and other script information.

Addded the ability for scripts to create menus in the Window-Eyes Control Panel (under a new Script Menus pulldown). This provides an easy method for accessing script help, options, or whatever the script author wants to make available without having to enter the Script Manager dialog first, or use some hotkey (although both of those options are still available).

Added a Menu object which lets you access/modify custom menus (for both script dialogs and in the Window-Eyes control panel) and their items.

Clips collections (and, therefore, clips themselves) can now either be dynamic or static. The ability to create a static collection of clips means being able to traverse the clip information even if those clips disappear from the screen. This gives you the ability to take a snapshot in time without the fear of the clips going away from under you. To support the new static clips collection, new methods have been added to the Text object for line, sentence, and paragraph that make the returned clips collection static. More specifically, they are: SentenceStatic, ParagraphStatic, LineStatic, PriorSentenceStatic, NextSentenceStatic, PriorParagraphStatic, NextParagraphStatic, PriorLineStatic, and NextLineStatic. You'll notice when you get a normal clips collections (outside of the text object) you can still use the same methods/properties.

Added Application.AttachWindowMessage. AttachWindowMessage lets you monitor any window message. For example, say you want to know if a window has changed position. Since there is no Window object event that fires when that change happens, you can instead hook the WM_WINDOWPOSCHANGED window message using AttachWindowMessage, and receive notifications when the window you're interested in is moved.

Added Utilities.TypeName - This mimics the TypeName function in VBScript. This is useful for languages, like JScript, that have no decent method of determining the true type of an object.

Added Application.OnCursorKey. This event mimics the existing OnHotkey event, only for cursoring keys instead. This means you will get this event before the application sees the key (so you can do things ahead of time) and you'll get the event after the application sees the key but before Window-Eyes. You can choose to let Window-Eyes process the cursoring key, or perform your own actions instead.

Added Keyboard.RegisteredHotkeys and Keyboard.RegisteredHotkey - RegisteredHotkeys returns a collection of all registered hotkeys, regardless of what script registered them. RegisteredHotkey then has properties such as Key, FilterBy, and Script.

Added Script.ConnectObjectWithParameter and Script.ConnectEventWithParameter methods.

Added Application.LicenseType, and Application.CopyProtection to indicate those two properties of Window-Eyes.

Added Application.MenuActive to indicate whether or not a menu is active, and if so, whether or not it's a context menu.

Added Application.CurrentLocaleID which returns the current OS locale ID (i.e. 1033 for English (United States))

ClientInformation.Overlap is now a read/write property. If you associated a script to an application whose initial overlap window was destroyed (such as MS Project, with an overlap splash screen that closes as the application launches), then you were unable to restart, stop, disable, or unload the script. Now, if the overlap is needed for any function, and it is found to no longer exist, another overlap for the application is automatically selected. This resolves the aforementioned problem. It is still possible, however, for the initial overlap window or subsequent overlap window to be invalid. To combat that problem, we made ClientInformation.Overlap read/write, meaning you can now set the Overlap for the application to any overlap you want as long as it is a true overlap and it is in the application's process. If you try to set it to a window that does not match that criteria, the change will be ignored.

Added CursorKeyAction.Execute which can be used to perform a given cursor key action. On a side note, the cursor key actions ckaOfficeSmartTab, ckaOfficeAttributeStatus, and ckaWordEnhanced can be executed as hotkeys hkOfficeSmartTab, hkOfficeAttributeStatus, and hkWordEnhanced. To allow this we added hkWordEnhanced, hkOfficeAttributeStatus, and hkOfficeSmartTab to the HotkeyID enum

Added Braille.UnicodeToDotPattern method, which takes a Unicode value and gives you back a string indicating the dot pattern of that character.

Added BrailleControlInformation.LineModeIncludeDataIndicators, LineModeLeftIndicatorDotPattern, LineModeRightIndicatorDotPattern, and SpeechBoxModeCharacterLimit.

Added StringToUnicodeBraille and DotPatternToUnicodeBraille methods to the Braille object. We've also deprecated DotPatternToUnicode in favor of the better named DotPatternToUnicodeBraille method.

Dialog.Control with no parameters now returns the control object for the dialog itself.

Added Process.Is64Bit which indicates if the process is 64-bit or 32-bit.

Added Clip.IsValid and Clip.IsStatic properties to indicate if a clip is valid and static (respectively).

Updated WindowEyesScriptingErrorCodes enum

Added menuSelection to the DialogEvent enum

Added MenuItemFlags, MenuActiveStatus, WindowEyesCopyProtection, and WindowEyesLicenseType enums

Added wtStatus to the WindowType enum, and support for status bar windows through scripting.

Added two treeview event enums: selectionChanging and itemExpanding.

Static text elements will now resize themselves automatically in scripting/XML dialogs, taking word wrap into account.

Optional parameters used as return values can (and must) now be passed as objects. For example, if you have a variable that you want to modify inside of a dialog proc, you have to pass that variable as a member of an object in the Dialog call, and not just as a variable itself. Refer to the DialogProc documentation for more information.

Added IsRunning property to the GWSpeak object. Note this object is different from the Window-Eyes Application object. You can use this property to determine if Window-Eyes (post 7.02) is actually running. For example:

Set x = CreateObject("GWSpeak.Speak") If x.IsRunning Then ' Window-Eyes is running End If

-- Braille

Window-Eyes now provides three different Braille modes: Structured (the default that Window-Eyes always had), Line Mode, and Speech Box mode. In structured mode, only one control is displayed at a time. In Line Mode, the entire line of the active window will be displayed. For example, in the Run dialog, if the OK button has focus, the display will contain the OK, Cancel, and Browse buttons. You can select a routing key above any of the buttons to activate that control. You can use the Display Mode Rotor Braille Hotkey to rotor between all three modes. Less than, and greater than symbols will appear at the beginning of the display if additional text exists to the left or right, respectively, of what is currently shown on the display. Also note that Grade 2 Braille is disabled in line mode (as allowing it would not give you an accurate representation of exactly how things reside on the screen). When you rotor out of Line Mode, Grade 2 will be enabled again (assuming you had it enabled before entering Line Mode).

In Browse Mode, a single touch cursor will route to that specific position, and a double press will perform the default action. Pressing a touch cursor twice in rapid succession on a link will activate the link

Window-Eyes now supports Turkish Braille tables.

Added support for the APH Refreshabraille display.

++ Enhancements Between Window-Eyes 7.01 and Window-Eyes 7.1

We fixed a problem where Window-Eyes would cause applications that launch themselves multiple times (for example, some console applications) to run slowly.

Window-Eyes now does a much better job of determining the overlap window associated with an application.

If you selected a sound card other than the default for, say, the DECtalk Access 32 (Window-Eyes) synthesizer, and then changed to another synthesizer, when you went back to the DECtalk Access 32 (Window-Eyes), the sound card would be set back to the default. This problem has been resolved.

We fixed a problem where pressing Enter did not activate the correct button in the Key Label Dictionary dialog

We fixed a problem where Read to End would not stop in the correct location when pressing the Control key.

Window-Eyes is now much more accurate when reading field names for buttons, check boxes, and radio buttons.

We fixed a problem where Window-Eyes would fail to operate correctly when a machine came out of Standby, Hibernation, or when exiting a screen saver, and being prompted for a password.

Window-Eyes would not shut down correctly when switching between Window-Eyes users. This problem has been resolved.

Window-Eyes now supports static boxes that behave like links.

We fixed a problem where Window-Eyes would not read focused items in places like Internet Explorer 8, and NOD32 4.0.

We fixed a problem where Window-Eyes would GPF if we got a window create on a window with a null name.

On some machines, Window-Eyes would fail to launch, and instead display a message box stating something to the effect of, "Unable to find user's directory." This problem has been resolved.

Whenever a new .WE file was created (for example, by saving Context Sensitive Help, or reclassing a control), the file would get created as ANSI. Now it gets created as Unicode.

We fixed a problem where key label entries were not being removed, even when using the remove button in the key label dictionary dialog.

It was possible, with Before Startup enabled, for Window-Eyes to keep some system services from launching correctly. This problem has been resolved.

We fixed a problem where reading Window-Eyes path information from relevant environment variables, or the registry, to find the path to Window-Eyes or one of its parts, would cause issues when running Window-Eyes mobile on a system with a full copy of Window-Eyes installed (such as Insert-Tab not working in Internet Explorer).

We fixed a problem where you were unable to enter certain characters using non-English keyboard layouts.

The applications listed in the Document Specific Settings dialog were sometimes not determined correctly. This problem has been resolved.

We fixed a problem where the registry entries for the Window-Eyes sounds in the Sound Control Panel were broken. These keys, however, will not be modified automatically if they are already incorrect. In other words, if you currently have this problem, you will need to manually fix each key, or remove the HKEY_CURRENT_USERAppEventsAppswineyes key, which will cause Window-Eyes to re-create them correctly the next time it runs.

We fixed a problem where you could execute the Load Set hotkey at the login screen, or other secure desktops.

The "Default" users directory name can now be localized.

We fixed a problem where you couldn't switch voices successfully when using the dedicated Eloquence synthesizer (even though you could by modifying the tone).

ANSI graphic dictionaries converted to Unicode would cause graphic labels to go missing. This problem has been resolved.

WE fixed a problem where the desktop could redraw over, and over, and over, and over, on Window-Eyes launch.

In Vista's start menu, if you searched for "c" and then arrow through the options, Window-Eyes was silent on the "group" names. This problem has been resolved.

We fixed a problem where some installation programs would not finish completely with Window-Eyes installed (even when Window-Eyes was not running).

If you set capitalization to Say Cap, and then typed in a password edit box, you would hear, "Cap star" for the shifted letters. This problem has been resolved.

We fixed a problem that caused hook errors when running Window-Eyes with the latest ZoomText.

We resolved a problem in the Winamp Library that would cause a GPF.

Window-Eyes would not automatically restart under specific circumstances after a hibernation or suspension. This problem has been resolved.

We fixed a problem where Window-Eyes would not read the reminder field in Outlook 2007 when using the Up and Down Arrow keys.

We fixed a problem where Window-Eyes would not read drop down and combo box choices if the combo box wasn't initially expanded.

We fixed a problem where arrowing up and down in the Lotus Notes Inbox was not working properly.

We fixed a problem where Next/Prior Character/Line/Word would not work in edit boxes.

We fixed some minor localization issues.

-- Set File Updates

You will need to re-install these sets from the Set File Manager to load the new versions.

* Notepad
o Added additional key labels such as Control-N, Control-O, Control-S, etc.
o Added additional cursoring keys such as home (character after), control-home (line), and f3 (line).
o Set the cursor delay to 1 under the general menu.
o Added application help when pressing control-shift-question.
* Windows Explorer
o Shift-arrows and shift-control-arrows are now defined as cursoring keys to read selected text when editing file names.

-- Scripting

If you had a hotkey registered for a certain window and while that window had focus you went into a menu bar we left the hotkey active. Now the hotkey will not fire if you go into a menu from the focused control that had the hotkey registered to.

The Package Manager now remembers paths when creating a script package.

We fixed a problem where focus and activation would get lost when starting and stopping scripts in the Script Manager.

We fixed a deadlock that could occur when connecting to ClientInformation.OnShutdown.

We fixed a problem where the Clipboard.Text was getting cleared accidentally.

When restarting a script that was displaying a script error, Window-Eyes could potentially deadlock. This problem has been resolved.

We fixed a problem where the Package Manager dialog would not gain activation when accessing it with Alt-Tab.

We fixed a problem where the registration of the external COM object thread wasn't happening correctly.

It was possible for a script to not successfully restart, but you'd still hear the restart message. This problem has been resolved.

We fixed a problem where ClientInformation.UILanguage was not getting set correctly if no language was set explicitly in the associated XML.

If an OnBlah event handler returned Nothing/Success, that meant it wanted to opt out of the replacement without copying the string. If multiple scripts did that, we would end up with NULL for the final string, effectively disabling speech. This problem has been resolved.

We fixed a problem where getting a usable DOMNode from a BrowseMode text line was less than successful.

OnError should no longer pass blank error descriptions. It now works like the script error dialog to lookup error descriptions.

The Text object's line, paragraph, and sentence now do a better job of setting the correct point used to obtain the text.

Scripts that are loaded by other scripts and then self-terminate are now correctly reported as stopped in the Script Manager.

We fixed a problem where EditBox.CharAtPoint was always returning 0.

Adding a key label entry to a key label dictionary was broken using the KeyLabelDictionary object's Add method. This problem has been resolved.

Window-Eyes will now automatically close any script error dialog that is displayed when Window-Eyes is shutting down.

Window-Eyes no longer uses the OSM to obtain window types for controls in scripting dialogs. This is much more efficient and resolves an occasional timing problem where you could not access/modify dialog information (such as setting the window title), or any of a dialogs controls, during the dialog's OnCreate event.

There were times the filtering of MSAA events through ConnectEvent wasn't being used properly so you would get events outside of your filter. This problem has been resolved.

We fixed a problem where an application specific script could continue to run, even after the associated application was closed.

Braille.DotPattern will now return an error if no braille display is enabled.

We fixed a problem where Speech.Speak could be silent if Braille was on.

We resolved a problem where you could not install scripts under an operating system username using a non-Latin character.

The LoadedScripts object was not functioning correctly under Windows Vista. This problem has been resolved.

We fixed a problem where the Lookup method of an ActiveCharacterDictionaries object would always return nothing, even when a valid entry existed.

If you passed ActiveWindow to a Dialog call, the dialog would be successfully parented to the active window. If you passed a variable that contained a copy of ActiveWindow, it would not work. This problem has been resolved.

When specifying a listview with checboxes in a scripting dialog, we now default to a state of no for all istview items. Also, the "none" property for checked didn't make sense, since you can press the space bar to clear it, then never get back to it. So we removed it.

We fixed some permission issues under Windows Vista in regards to CreateObject.

We have resolved all known issues with VB.NET external applications/scripts.

We fixed a problem where we were blocking some MSAA events for global scripts.

Scripting/XML dialogs are now always made active when shown.

We fixed a hang that would happen when trying to get version strings through scripting.

We fixed the "the remote server has gone away" script error on System Shutdown.

We fixed a problem where Braille.Translate would cause Window-Eyes to hang.

We fixed a problem where Hooking OnProcessCharacterDictionary would break punctuation.

BrailleDisplay.OnKey reports there are never any actions. This problem has been resolved.

We fixed a memory leak in Screen.PixelColor.

-- Microsoft Office

The Outlook 2007 Calendar would not display the correct information if a message was open. This problem has been resolved.

Window-Eyes can now use cursor keys in the font combo box of the Office ribbon.

In Outlook 2007, when changing panes using F6, Window-Eyes would not announce the name of the current folder.

-- Browse Mode

We fixed a problem where the default button would get lost when adding placemarkers.

Mozilla changed the way events are handled in frames between Firefox 2 and Firefox 3. Window-Eyes now accounts for that change.

We fixed a problem where dialogs, such as the Window-Eyes Mouse Find dialog, would cause Browse Mode to reload after closing.

We worked around a Mozilla change to Firefox that would cause Placemarkers to not work until the Placemarker dialog was opened and then closed.

Window-Eyes now provides better support for edit boxes in both Internet Explorer and Firefox outside of Browse mode.

-- Braille

In a listview, column titles and field data would not match up under some circumstances, such as hiding the first column header. This problem has been resolved.

We fixed a problem where the Braille hotkey dialog would open slowly. Now, Braille hotkeys are loaded quickly, causing the dialog to open much faster. Saving Braille changes also happens much more rapidly.

We fixed a problem where multiple listview items were being highlighted.

We fixed a problem where long contiguous lines of text would not be displayed properly if Whole Word Mode was enabled.

In Excel, a quick message could get into a loop, and never display the cell's contents. This problem has been resolved.

Quick message mode would only show the most recent quick message. Now, if you get several quick messages before the last one expires, all of them will be shown.

If you arrowed too quickly through an Excel spreadsheet, the text of the final cell wouldn't show up on the Braille display. This problem has been resolved.

We fixed a problem where Grade 2 whole word mode would skip text when moving right by block.

We fixed a problem where Braille would constantly adjust the left edge of the display when using a Braille movement key. This problem has been resolved.

Reclassed edit boxes could cause garbage characters to be shown on the Braille display. This problem has been resolved.

We fixed a problem where group boxes in Braille could have their first character truncated.

Braille can now display both group box names and field names at the same time.

We fixed a problem where routing mouse to focus would cause the mouse and caret to be on different cells.

We fixed a problem where the cursor would not update in Braille when Show Indents and Show Extra Spacing were enabled.

Pressing a routing key to toggle the checked status of a check box was not working. This problem has been resolved.

Combo boxes were not being displayed correctly (or speaking correctly, in some cases) in Internet Explorer 7 and Internet Explorer 8. This problem has been resolved.

With the control information option Include Name off, the braille display would be blank in the Thunderbird message list. This problem has been resolved.

If a reclassed listbox had a field name, we would highlight it in Braille. This problem has been resolved.

Launch Wordpad and set up a Braille hotkey for the "to statusbar" hotkey. Press this Braille hotkey, and the mouse pointer goes to the top left of the screen. This problem has been resolved.

We fixed a problem where the Windows Calculator displayed an empty, read only, edit box.

We fixed a problem where selected text in browse mode was not highlighted in Braille.

Selected text in Notepad was not showing up as highlighted with dots 78 in Braille. This problem has been resolved.

We fixed a problem where reading with the mouse would cause "stuttering" with Braille.

We fixed a problem where Braille Whole Word Mode was not functioning correctly.

Using continuous search in Notepad (F3) in Structured Mode would result in a blank display.