Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 15378

Summary: Accessibility API does not work for getValue for a shell
Product: [Eclipse Project] Platform Reporter: Tod Creasey <Tod_Creasey>
Component: SWTAssignee: Carolyn MacLeod <carolynmacleod4>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 Keywords: accessibility
Version: 2.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard:
Bug Depends on:    
Bug Blocks: 15320    

Description Tod Creasey CLA 2002-05-06 17:30:25 EDT
If you want to use getValue to update the value of the text for a Shell this 
does not currently get propogated out even though it does get called.

I added the following to the configureShell method in 
org.eclipse.jface.dialogs.MessageDialog

shell.getAccessible().addAccessibleControlListener(
   new AccessibleControlListener() {
         public void getValue(AccessibleControlEvent e){
	   String readValue = shell.getText() + message;
	   e.result = readValue;
}	

The method was being hit but when I looked at the Shell text using inspect32 it 
was only the visible text on the shell that it found. It appears the change is 
being looked up but not propagated.
Comment 1 Carolyn MacLeod CLA 2002-05-07 11:43:18 EDT
It is actually working, but not if you hover over the title bar of the shell.
If you hover over the client area of the shell, you will see the new value.
Unfortunately, focus is the real problem for your dialogs. The dialog button 
gets focus, and the value of the shell is never read. I am looking into this to 
see if there is anything I can do to get dialogs to work properly.
Comment 2 Tod Creasey CLA 2002-05-08 13:00:27 EDT
Look at the Detect and Repair Dialog from Word (in help menu). It is a dialog 
based on a window and looks a lot like our project delete dialog and does work 
with JAWS.
Comment 3 Carolyn MacLeod CLA 2002-05-21 00:31:16 EDT
Deferred to fix pass 1
Comment 4 Carolyn MacLeod CLA 2002-05-30 17:38:49 EDT

*** This bug has been marked as a duplicate of 15559 ***