Hi, Pete. The reason is to save an extra call. From my understanding AT wants to know the caret offset within deepest accessible having a caret. This doesn't add complexity to server implementation (as you said all it's needed is to query text interface and call caretOffset). We could introduce magic value for caret offset argument to specify that the server shouldn't calculate it.
Thank you. Alex. On Sat, Sep 3, 2011 at 5:39 AM, Pete Brunet <[email protected]> wrote: > Alex, Why does accessibleWithCaret have an [out] caretOffset? The user can > QI to IAText and use IAText::offset. I propose not adding that redundancy > (and thus extra code for the app developers). -Pete > -- > Pete Brunet > > a11ysoft - Accessibility Architecture and Development > (512) 467-4706 (work), (512) 689-4155 (cell) > Skype: pete.brunet > IM: ptbrunet (AOL, Google), [email protected] (MSN) > http://www.a11ysoft.com/about/ > Ionosphere: WS4G > > _______________________________________________ > 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
