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
