Bug 14847 - Accessibility - cannot fire accessible state changed
Summary: Accessibility - cannot fire accessible state changed
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 major (vote)
Target Milestone: ---   Edit
Assignee: Veronika Irvine CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2002-04-29 10:55 EDT by Randy Hudson CLA
Modified: 2002-09-11 09:48 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Randy Hudson CLA 2002-04-29 10:55:42 EDT
Accessibility callbacks only occur when focus traversal happens.  However, I 
have a single canvas that has several items which can be traversed, like a 
windows tree. I need to fire whenever such traversal happens so that the 
accessiblity callbacks will be refreshed.  i.e., focus location, role, etc.
Comment 1 Carolyn MacLeod CLA 2002-05-20 16:03:29 EDT
Try using the setFocus API on Accessible.
An example is in CTabFolder.
I have not had time to write up that little example for you - sorry.
I will get to it sometime, but I'm afraid I have other things to do first.
Please let me know if this helps.
The API and the changes to CTabFolder were released a couple of drops ago.
Comment 2 Carolyn MacLeod CLA 2002-05-21 13:51:39 EDT
Note that there was a bug in Accessible.setFocus which is now fixed in the M6 
drop that will be available today.  If setFocus(ACC.CHILDID_SELF) was sent to 
the client, I was sending the parent window info instead of "self".  Hopefully 
this was a rare case and you were typically using setFocus(aChildID), but if 
you needed this to work also, please get the latest drop (20020521 - afternoon).

On a side note, I believe you only need setFocus in order to call this PR 
fixed. If you find that you need setSelection as well, please make a case for 
why we should add it as API. The other notification messages are esoteric, 
because typical clients will ask for info when the mouse moves or focus changes.
i.e. it would be very strange for you to be generating role & location change 
notification messages - it would slow your code down making sure to generate 
everything when you were just going to be asked again anyhow when the changed 
item gets focus.

Please let me know if I can mark this PR fixed.
Comment 3 Randy Hudson CLA 2002-09-11 09:20:23 EDT
Isn't this fixed?
Comment 4 Veronika Irvine CLA 2002-09-11 09:48:05 EDT
Fixed in 2.0.