Java Accessibility Documentation: AWTMonitor Example

JAVA ACCESSIBILITY

AWTMonitor Example

Version 1.0

March 1998

[Home] [What are they?] [Overview of API Features] [API Reference] [FAQ] [Examples] [Changes] [JFC Home Page]

The AWTMonitor example allows you to obtain information about AWT objects being displayed on the screen by a particular Java^TM Virtual Machine. It does not require the Java Foundation Classes to run. To run AWTMonitor you need to have obtained and installed the JDK1.1.5 or better.

For those interested in detail on the additional accessibility features of the Java Foundation Classes, we recommend using JavaMonitor instead of AWTMonitor. JavaMonitor provides all the capabilities of AWTMonitor, but also has additional support for the JFC classes.

Snap shot of AWT Monitor in action.

Preparing To Run AWTMonitor:

AWTMonitor is in the examples/AWTMonitor directory included with this release of the Java Accessibility Utilities (click here to view the source). Before you can run it, you need to set up your environment appropriately by following these instructions:

Modify your CLASSPATH environment variable so the jaccess.jar file that comes with this kit is included in the path.

Modify your CLASSPATH environment variable so the examples/AWTMonitor directory that comes with this kit is included in the path.

Modify your $JDKHOME/lib/awt.properties file to include the following lines:
AWT.EventQueueClass=com.sun.java.accessibility.util.EventQueueMonitor
AWT.assistive_technologies=AWTMonitor

After you follow these instructions, you should be ready to run AWTMonitor. If you did not set up your CLASSPATH correctly you might get one of the following errors when running a Java^TM application:

Failed loading com.sun.java.accessibility.util.EventQueueMonitor: 
java.lang.ClassNotFoundException: 
com.sun.java.accessibility.util.EventQueueMonitor

Error trying to newInstance AWTMonitor java.lang.ClassNotFoundException: 
AWTMonitor

The first error means the jaccess.jar file is not in your CLASSPATH, and the second means the AWTMonitor directory is not in your CLASSPATH.

Running AWTMonitor:

By following the instructions above, AWTMonitor will automatically be started any time you start a Java application.

Using AWTMonitor:

AWTMonitor provides a several rows of checkboxes at the top of its dialog box. These allow you to specify the classes of user interface events you can monitor in the Java Virtual Machine. AWTMonitor registers an interest in the events by using calls to the AWTEventMonitor class from the Java Accessibility Utilities package whenever you click one of the checkboxes.

In the middle of the dialog box is a List of events that is updated as each event occurs. Items will be posted in this List only if you selecting the events you are interested in by manipulating the checkboxes at the top of the box.

In the bottom left of the dialog box is a small List box that represents the last object to have focus. It is updated each time the focus changes and contains a small sample of the information obtained from the Java Accessibility API. NOTE: This box will not be updated unless you select for Focus events.

In the lower right of the dialog box is a small List box that you can populate by moving the pointer over an object and pressing the F1 key. This uses calls to EventQueueMonitor to obtain the current mouse position and obtain an accessible object from that point. It then calls a small number of methods from the java Accessibility API to display information about the object under the pointer. NOTE: This box will not be updated unless you select for key events.

To submit comments or suggestions about Java Accessibility, please send mail to access@sun.com.