We are not speaking from the OnChildFieldName function, no. I did think of checking for that one.
I don't think this code has any other handlers relevant to this problem that could be producing speech either. We do have an OnChildSummary event, but it does not try to get a field name as far as I know. I think I need to look more carefully into that function though... On Mon, May 02, 2011 at 03:23:16PM -0400, Chip Orange wrote: Doug, Just a couple of questions ... you aren't actually speaking the field name in your handler are you? you're presumably just returning it as the string value of the function? Also, when the user arrows in this control, is it stimulating any of your other handlers? would you be doing anything as a result of the arrow keys such as causing the summary to speak? I found myself in this type of situation some years ago, and it turned out that some other action I was taking was unknowingly causing the field name event to fire (I think I was doing something with the summary command). At the time I thought the field name event was misbehaving, until Doug explained to me whatever i was doing was causing field name to fire. Chip Chip -----Original Message----- From: Doug Lee [mailto:[email protected]] Sent: Monday, May 02, 2011 10:47 AM To: [email protected] Subject: Issue with using OnChildFieldName to name a combo box Apologies, per usual, if I'm missing something obvious here. This time, my following question comes from working with someone by phone; so I have not seen this situation myself yet... We have a combo box for which our general OnChildFieldName event function is called in at least the following three situations: - On the user typing Ctrl+Shift+N. - On the user tabbing into the box. - On the user arrowing through choices in the box. The last of those surprised me. I have generally thought that intercepting OnChildFieldName would be a good way to name a field when there is any reason not to use Ctrl+Insert+F to do it. However, intercepting OnChildFieldName here, besides the benefits of making Ctrl+Shift+N and Tab work, causes WE to say the name on every arrow through options in the combo box. This raises two general questions: First, is OnChildFieldName a recommended way to name a field? Second, is it by chance or design that arrows, which fire ValueChange but not FocusChange events, cause OnChildFieldName to fire? -- Doug Lee, Senior Accessibility Programmer SSB BART Group - Accessibility-on-Demand mailto:[email protected] http://www.ssbbartgroup.com "While they were saying among themselves it cannot be done, it was done." --Helen Keller -- Doug Lee, Senior Accessibility Programmer SSB BART Group - Accessibility-on-Demand mailto:[email protected] http://www.ssbbartgroup.com "While they were saying among themselves it cannot be done, it was done." --Helen Keller
