1.0 Known problems and limitations
1.1 Disposing in a
focus event
1.2 List and ComboBox on Windows(R) NT
1.3 BiDi support
1.4 Cursor constructor arguments
1.5
Javadoc not consistent across platforms
1.6
JAWS requires MSAA for List Views to read checkboxes in Tables
1.7 JAWS screen reader does not read
WebSphere Studio dialog boxes properly
Applications should not dispose widgets in focus changing events. Doing so occasionally results in an SWT exception being thrown.
On Windows NTR only, you should avoid creating items in a List
or ComboBox
with strings longer than 1000 characters. Doing so may result in a General
Protection Fault.
The StyledText
widget provides bidirectional language support for
Hebrew and Arabic locales. Currently this support is available only on Windows
and has several known problems.
In the constructor Cursor(Device device, ImageData source, ImageData
mask, int hotspotX, int hotspotY)
, when both a source and mask argument
are specified (that is, the mask is not null), the meaning of the two arguments
is reversed. That is, the mask
argument should be the source image
and the source
argument should be the mask image.
The Javadoc for protected methods is not consistent across platforms. The Javadoc for the Windows platform, which is used to generate the documentation that appears in the Platform Plug-in Developer guide, is the definitive source
In order for JAWS to detect the checkbox information in Tables, MSAA support for List Views must be activated as follows:
- Open WebSphere Studio and click INSERT + F2.
- In the Run JAWS Manager dialog select Configuration Manager.
- Select Set Options and then select Advanced Options.
- Select the Rely on MSAA for List views check box.
- Click OK.
- Click File > Save.
There is a known problem with the JAWS screen reader (up to version 4.5) whereby its "Read Box in Tab Order" command (Ins+B) does not read all controls in WebSphere Studio dialogs.
Return to the main readme file
(C) Copyright IBM Corporation 2000, 2003. All Rights Reserved.