New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
office 2010| selected symbol in insert symbols dialog is not read in word and excel #3538
Comments
Comment 1 by manish on 2013-09-21 11:18 The graphic object itself does not expose any of the iaccessible properties (name, value, description, display text etc) with any useful information. Within the symbols dialog, there is a rich edit field that displays the hex unicode value of the selected character. Every time a different character is selected, the value displayed in this richedit box changes and this box raises a value changed event. The value property of the field is the hex value of the unicode character.
In approach 1, we are using an event raised by and the value of a control other than the one the user is directly manipulating. in approach 2, the solution is independent of any other control but we are doing more work in the form of gesture bindings etc. Also, for the string to be actually spoken in approach 1, we can also use To identify the richedit field and assign it a special class that handles the value change event, can we use in IAccessible.init.findOverlayClasses: |
Comment 2 by manish on 2013-09-22 07:43 The keyboard binding approach is at: and the richedit field value change approach is at: Please review and pick whichever looks more correct. |
Comment 3 by manish on 2013-09-22 07:48 |
Comment 5 by manish on 2013-10-03 05:10 |
Comment 6 by mdcurran (in reply to comment 5) on 2013-10-03 05:18 |
Comment 7 by manish (in reply to comment 6) on 2013-10-04 04:51
|
Comment 8 by mdcurran (in reply to comment 7) on 2013-10-04 06:08
|
Comment 9 by manish (in reply to comment 8) on 2013-10-05 05:04 There was no good reason not to use __gestures. I just saw both styles used in existing code and thought of avoiding the repetition of the script name, which is the same for all gestures.
|
Comment 10 by Michael Curran <mick@... on 2013-10-06 22:59
Changes:
|
Comment 11 by mdcurran on 2013-10-06 23:07 |
Comment 12 by manish (in reply to comment 11) on 2013-10-07 04:44
The deviation I did from above for t3538-kb was that I created it from next, which I'll avoid in the future. -Manish
|
Comment 13 by mdcurran (in reply to comment 12) on 2013-10-07 04:59 |
Comment 14 by jteh on 2013-11-01 01:50
Sorry i didn't get a chance to look at this properly sooner. |
Comment 15 by manish (in reply to comment 14) on 2013-11-01 17:41 Thanks,
|
Comment 16 by jteh (in reply to comment 15) on 2013-11-01 22:16
Thanks. I recognise that point 3 might not be fixable, but give it a shot. Point 1 definitely needs to be fixed.
Ah., Thanks for explaining. It was probably just a misunderstanding on our part; we only had time to look briefly. One question, though: many users seem to select something from a list, then tab to the button to close the dialog, rather than just pressing enter on the list item. I assume that if you do that in this case and you're on the first list, you will lose your selection, since the first item in the second list will get focus and therefore get selected? It isn't our responsibility to change this, but I'm curious. |
Comment 17 by Michael Curran <mick@... on 2013-11-27 01:54
|
Comment 18 by Michael Curran <mick@... on 2013-12-12 04:19
Changes:
|
Comment 19 by mdcurran on 2013-12-12 04:21 |
Comment 20 by ondrosik on 2014-02-05 07:29 |
Comment 21 by blindbhavya on 2014-10-03 13:31 |
Reported by manish on 2013-09-21 10:47
NVDA does not read the symbols as a user selects them using the arrow keys in the insert|symbols dialog box in office applications in Word 2010 and Excel 2010.
The text was updated successfully, but these errors were encountered: