In this light reverse API makes more sense - disable what you don't need :) The problem is to decide what to enable/disable and perhaps proper engine creation to track what was requested by AT and what wasn't, and watch lifecycle of AT.
Alex. On Tue, Jun 22, 2010 at 3:00 AM, James Teh <[email protected]> wrote: > On 22/06/2010 2:14 AM, David Bolter wrote: >> IApplicationAccessible >> - setRequestedSupport([in] long supportBitflag, [out] long >> supportedBitflag); >> This API suggestion is just illustrative. Something like this would >> allow applications to provide needed support without wasting performance >> by also providing unused support. Thoughts? > This sounds okay. The problem is that in order to preserve backwards > compatibility with older ATs which don't know about this new API, apps > will have to enable everything by default anyway, which rather defeats > the purpose. > > Jamie > > -- > James Teh > Vice President > NV Access Inc, ABN 61773362390 > Email: [email protected] > Web site: http://www.nvaccess.org/ > _______________________________________________ > 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
