Do AT's use IA2_TEXT_BOUNDARY_ALL?
Or do they use IAccessibleText::text(0, length, pbstrText) to retrieve all
of the text?
I am asking because:
1) ATK does not have this boundary type, so it just adds confusion.
2) Technically, we don't need it because IAccessibleText::text(0, length,
pbstrText) already returns the whole text.
3) I have to special case IA2_TEXT_BOUNDARY_ALL in 3 places:
IAccessibleText::textAfterOffset, textAtOffset, and textBeforeOffset, and
in each case, I have to ignore the offset parameter (which feels awkward),
and determine the length of the text (which is an extra call to the
application above me).
4) It feels redundant to have 4 different ways of asking for the whole
text.
If there is some special reason to keep IA2_TEXT_BOUNDARY_ALL (maybe
because AT's can save a call if they don't have to ask for the length?),
could we please only allow it in one place, i.e. perhaps in textAtOffset
only? Then just document that textAfterOffset and textBeforeOffset don't
support the IA2_TEXT_BOUNDARY_ALL type?
I am tempted to return E_INVALIDARG if get boundaryType ==
IA2_TEXT_BOUNDARY_ALL in textAfterOffset and textBeforeOffset. Would that
break anybody?
Carolyn
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
