Community
Participate
Working Groups
Build Identifier: 3.4.2 I have a selection listener attached to the combo that changes a value in a SWT Spinner when the combo value changes. The spinner value change some how triggers the JAWS accessibility tool to stop reading any further changes made to the combo. Using JAWS 11.0 to test and eclipse 3.4.2 as my development platform. Reproducible: Always Steps to Reproduce: 1. Create a Java class that uses SWT Combo and Spinner. The combo's selection listener should change the value of spinner 2. Start JAWS and run the Java class. 3. Using the keyboard tab to the combo box, and change the selection using the arrow keys. 4. Notice the spinner value change. Now use the arrow key to change the value in the combo again. JAWS will not read anything else in the combo.
Created attachment 182926 [details] Java snippet
Hi. I agree that this is very strange. It seems that setting the value of the spinner redirects the accessible focus over to the Spinner. This is unexpected. All I have for you at this time is a work-around. Note that this is not a fix, and I will leave the bug open to look at again in future. After the line: spinner.setSelection(2); Please add the line: validationCombo.getAccessible().setFocus(ACC.CHILDID_SELF); This forces the accessible focus back to the combo, and JAWS rereads the combo item. I am afraid that I do not have time for anything more than this work-around at the moment. I hope it helps.
Hi, Thanks for the work around. Although it does help the problem, I noticed the work around at times skips reading some entries but reads others fine. This is not happening always though. Plus it reads the label for the combo box each time I change selections which could get annoying to the user.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
