Window-Eyes: Performance, Reliability, and Stability
"Unleashing the power of your mind's eye."
(C)1995-2010 GW Micro, Inc. All Rights Reserved
E-Mail: wesupport@aisquared.com
Phone: 260-489-3671
Released: 5/5/2010

[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.2

GW Micro is proud to announce the release of Window-Eyes 7.2. This version of Window-Eyes introduces full support for Microsoft Office 2010, significant speed enhancements, and some serious stability improvements. We take our motto of performance, stability, and reliability seriously, and this version of Window-Eyes demonstrates that commitment.

Keep reading to learn more about Window-Eyes 7.2, 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 a GW Micro e-mail list? There are several to choose from: GW-Info for lively discussions of GW Micro products and services, GW-News for GW Micro news announcements only, GW-Scripting for Window-Eyes script developers and users, and many more. To subscribe, unsubscribe, or manage an existing subscription, visit http://www.gwmicro.com/listserv. Subscribing is as simple as entering your email address in the email address edit box, selecting the Subscribe/Default radio button, selecting the GW-Info email list from the combo box of available lists, then selecting the Modify button. You will then receive a confirmation message. Select the link provided in the confirmation email, 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 egaer 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.X (including 7.0, 7.01, 7.02, 7.1, or 7.11) installed before installing Window-Eyes 7.2.

2. Window-Eyes 7.2 will not install over 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 upgrade to Window-Eyes 7.2 by contacting our order department at 260-489-3671, or orders@aisquared.com.

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.2

Window-Eyes now fully supports both 32-bit and 64-bit versions of Office 2010. One of the more significant features of Window-Eyes support for Office 2010 is UIA support for the Outlook 2010 message list views (such as the Inbox).

Several performance enhancements have been made. Window-Eyes 7.2 now launches much faster when using Windows Vista or greater. Navigating list views is now much faster. In addition, cases like tabbing between address fields in Outlook Express have also been sped up. Each of these speed enhancements, coupled with the dramatic speed increase provided by the Window-Eyes Eloquence Performance Patch (now fully integrated), make Window-Eyes 7.2 much more efficient than previous versions, especially under the newer operating systems.

Added Braille.DisplayMode as a read/write property. This sets or returns an item from the new BrailleDisplayMode enum (bdmStructured, bdmLine, and bdmSpeechBox), allowing you to retrieve and set the current Braille display mode.

Added bhkRotorDisplayMode, bhkLeftOneCell, and bhkRightOneCell to the BrailleHotkeyID enum. This means you can now execute these hotkeys with the ExecuteBrailleHotkey method.

The Control.Id property is now read and write. Previously it was read only.

++Enhancements Between Window-Eyes 7.2 and Window-Eyes 7.11

--Miscellaneous

We fixed a problem where, upon booting, you were no longer able to bring up any windows or launch any applications. Thanks to Don Hert for lending us a machine to resolve this problem.

We fixed a problem where Window-Eyes would behave very slowly after logging in. Thanks to Chris Grabowski for lending us a machine to resolve this problem.

We fixed a problem where .NET checked list boxes were not reading correctly.

We fixed a problem where edit boxes would not gain focus correctly when turning Browse mode off on websites like bookshare.org.

Occasionally, on some machines, when alt-tabbing between applications, Window-Eyes would hang. This problem has been resolved.

We have fixed several general OSM related issues, along with specific problems in some applications, like IRead.

Resuming from standby mode in Window XP would cause Window-Eyes not to start automatically (if that option was enabled). This problem has been resolved.

We fixed a problem where the iTunes store was not loading in Browse Mode. You must have the latest version of iTunes for the store to work properly, as Apple resolved several accessibility issues on their side as well.

The suggestion lists in various Office spell check dialogs were not reading when they gained focus. This problem has been resolved.

We fixed a problem where some system services (such as the print spooler) would not start on some machines when Window-Eyes was installed.

Both Office and Windows 7 ribbons should now always work. Occasionally, they would not.

We fixed a problem where Windows 7 Explorer windows would speak all headers before speaking the focused item. Also, to more closely match existing listview behavior, Windows 7 list views now:
- Add "x of y items selected" to speak summary for Windows 7 items view
- Remove "of y" from individual rows in Windows 7 items view on speak summary

Using Windows Vista, or greater, if you set Eloquence to use the default sound card, and it changed, Eloquence would not adjust itself automatically. This problem has been resolved.

We fixed a problem where the Polish version of Window-Eyes would stop responding when copying files with Total Commander.

We fixed a problem where the top/bottom index was repeated under Windows 7.

If a track bar was contained in a group box with a name of 32 or more characters, the value of the track bar would repeat when it gained focus. This problem has been resolved.

We fixed a problem where Window-Eyes would lose track of module names under 64-bit Windows 7.

We resolved some issues with Prior/Next Character and Word in edit boxes.

Spelling non-ANSI characters phonetically resulted in unexpected speech. This problem has been resolved.

We fixed a problem where every other character was being skipped when using the mouse to read under Windows Vista or greater.

We fixed a problem where moving the mouse by character when renaming a file in Windows Explorer would not read under Windows Vista or greater.

Many times, under Windows 7, Window-Eyes would not see the mouse pointer move or notice mouse clicks from the physical mouse. This has been resolved.

We fixed a significant memory leak that caused Window-Eyes to consume more and more memory over time. Now, the total Window-Eyes memory usage is much smaller, and will no longer continue to increase unabated.

We fixed several, general OSM corruption issues.

Recently, we've seen systems that set the Window-Eyes mirror driver as disabled in the Device Manager, even after a successful installation. This causes Window-Eyes to indicate that it cannot communicate with the display driver on launch, and then immediately exit. Window-Eyes will now check to see if the mirror driver is disabled on launch, and if so, enable it before trying to attach to it.

We fixed a regression caused by the ZoomText compatibility fix where an RDP session on Server 2008 (and possibly others) would cause a BSOD when you logged in remotely into a session that previously had WE running locally.

We fixed a problem where Windows 7 would not update the display when Window-Eyes was loaded in a fresh login through an RDP session.

The Window-Eyes mouse search feature was not recognizing case of non ASCII letters. This problem has been resolved.

--Scripting

Window.CurrentUserWindowID and Window.CurrentHyperactiveWindowID were always using information from the active set file instead of the set file associated to the window being queried. This problem has been resolved.

Performing actions on a variable set to Keyboard.Keys would cause Window-Eyes to become unstable. This problem has been resolved.

If you hooked an MSAA event, and filtered it by process, you wouldn't get any events. This problem has been resolved.

If UAC is disabled, you can now successfully obtain an Application object using GetObject for any application. Previously, because the application was running at high integrity, GetObject would fail. Now you will only experience this when UAC is on, and you are attempting to use GetObject for an application that is running at high integrity (which is by design).

If a script placed itself in the Window-Eyes Scripts Menu pull-down and within its own dialog menu at the same time, you might have problems accessing the menu items, or setting menu item attributes (like checked). This problem has been resolved.

We fixed a problem where the CursorKey object passed to an onCursorKey event handler would not execute correctly.

GlobalSettings.EnhancedSupportForCurrentWordDocument did not return the right value, and you were not able to set it to anything. Now it works as it should.

There was a problem with XML dialogs that used menus while also using menu options from the Window-Eyes Script Menus pull-down. At best it would cause the Script Menus object to become permanently disabled until you restarted Window-Eyes. At worse it would cause Window-Eyes to crash. This has all been fixed.

We fixed a problem where LoadClassInformation would only load for objects with events (i.e. objects that implement IProvideClassInfo). Now it should work for any object, even one that's not a coclass, so long as the server implements ITypeInfo/ITypeLib.

We fixed a problem where the Type property value for certain window (status bars, up/down controls, etc.) were not calculated correctly. In addition, the scripting type enum was broken; Window.Type did not match the documentation or the IDL file. Everything has since been cleaned up, including the documentation.

Fixed bug where MSAAEventSource.BlockEvent would fail if you passed it a process object in a variable.

Synthesizer.Speak was still filtering the text before sending it to the synthesizer. Now this method will no longer filter the text, allowing you to send commands directly to the selected speech device.

The Clips.SearchText method excluded labeled graphics. This problem has been resolved.

The SetFile.Save method would throw an error instead of saving anything. This problem has been resolved.

We fixed a problem where an error would occur when obtaining dictionary information from a set file that did not have a dictionary associated to it.

If you try and change any property of a SetFile object but the object is no longer valid then we silently go on instead of throwing an error.

If you try to save a set file with something like Window.ActiveSettings.Save, and the file cannot be saved because, say, the file is read only, you now get an error.

The ExecuteHotkey method never worked for the hkWordEnhanced, hkOfficeAttributesStatus and hkOfficeSmartTab. Now they do. Also, the hkOfficeAttributesStatus needs to know which status to speak, so the second parm in ExecuteHotkey (KeyAction) is used to indicate which attribute by specifying a value from the OfficeAttributeStatus enum.

We fixed a problem where the ExecuteHotkey method did not validate the value it was given.

At times, reclassing a window by setting the Window.Type would not work. This problem has been resolved.

We fixed a memory leak caused by hooking some MSAA events.

Calling Mouse.ToFocus is now silent.

We fixed a problem where you were unable to set the sound card through scripting.

We fixed a problem where the BrailleHotkeys collection didn't work and caused stability problems.

Calling ExecuteHotkey with hkPriorWord would always result in the word being spelled. Now it correctly speaks the word, and the additional optional parameters function as expected.

The Keyboard.RegisteredHotkeys collection was not indexed; you had to use For Each to enumerate them. Now they have an index, ranging from 1 to the collection's count.

If you tried to get the NativeObjectModel object for a window that didn't support this property, you would get an error. Now it will return Nothing.

The default value for the returns property on read-only, multi-line edit boxes is now "no" (in scripting XML) since a return isn't going to do anything in a read-only edit box anyway.

--Braille

Using Line Mode in Notepad with the right combination of font and text size could cause the display to show blank lines instead of lines with text. This problem has been resolved.

We fixed a problem where Braille would not track correctly in Word 2007.

We fixed a problem where Windows Mail would become sluggish after arrowing quickly using line mode.

Both 6 and 8 dot Braille is now indicated for all languages in the Braille Translation Tables dialog.

In structured mode, Window-Eyes now displays the letter s on UIA list view items that are selected.

In Microsoft Word forms, as you tabbed between form elements, Braille did not display anything. This problem has been resolved.

When selecting items using Windows Explorer under 64-bit Windows 7, there was no indication of the selection on the Braille display. This problem has been resolved.

We have added support for the following Braille displays:
* PegasusDW
* VarioPro
* Audiodata BZ
* Audiodata BM

--Set File Changes

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

* Firefox
* Internet Explorer
* Kurzweil 1000
* Office 2000
* Office 2003
* Office XP
* Office 2007
* Office 2010
* Outlook Express
* Windows Explorer