You are absolutely correct Malte, and we likely would have provided this keystroke combination in order to be compatible with the a1 text model, but long ago Eclipse defined ctrl+up/down as "scroll up/down" and I gather that Eclipse users have grown used to having this feature (it is handy if you want to see what comes next without changing your selection... one very typical use is in the debugger).
However, anyone using StyledText for some other application (i.e. not Eclipse) could define those keystrokes as you described, or even as move forward/back paragraph if appropriate, because the basic StyledText control leaves those keystrokes undefined. Carolyn From: Malte Timmermann <[email protected]> To: [email protected] Date: 27/06/2011 04:49 AM Subject: Re: [Accessibility-ia2] IA2 text attributes - finalize? Sent by: [email protected] Hi Car, I guess it can't do any harm to make it optional, but just wanted to point out that the key combination also might make sense for a code editor. Not sure how Eclipse behaves, but in many editors, when you have line wrapping on a certain column or window border, you can't rely on key-up/down bringing you to the prev/next code line. So with Ctrl + key-up/down, you could have a reliable way to always change the code line, and not the visual line. Malte. Carolyn MacLeod wrote, On 24.06.2011 17:54: > >> 2a) Note that the important object attribute "text-model:a1;" is not > described at all. This really needs to be in the object attributes list > before that is finalized. >> I can add it. Is it as you have indicated or Iatext-model:A1as > documented in Brian's document at _ > __> > http://www.linuxfoundation.org/collaborate/workgroups/accessibility/ia2/ia2_implementation_guide_ > > > "text-model:a1;" is the exact spelling currently used in JAWS and Eclipse. > It was changed to that at your request, "for consistency with other > attributes". > If you need the background email discussion, I can forward. > > *Brian*, can you make this change to the "IAccessible2 Implementation > Guide" document, please? > The other related change that was needed (for StyledText to be perfectly > "a1") is to add the word "(optional)" to the end of this point in the > list of expected a1 keystrokes: > > * Ctrl + up and down arrows: Move between paragraphs > > StyledText cannot support paragraph navigation in Eclipse because it is > typically used for a code editor, and code does not have paragraphs... > so this keystroke pair needs to be optional. It was decided that that > was better than defining a whole new "a2" model just for one pair of > keystrokes. > > Thanks! > Car > > > > _______________________________________________ > Accessibility-ia2 mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
