suggestion below.
Rich Schwerdtfeger
CTO Accessibility Software Group
[email protected] wrote on 06/21/2010
01:00:38 PM:
> From: James Teh <[email protected]>
> To: [email protected]
> Date: 06/21/2010 01:13 PM
> Subject: Re: [Accessibility-ia2] a11y support registry API
> Sent by: [email protected]
>
> 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.
>
Would it be better to have a generic function like this to pass a string
representing the feature we are asking for?
RequestFeature([in] String feature, [out] long feature);
The string could be a set of features. If it were not supported in the
current implementation return a -1.
otherwise you return a value.
Some strings:
"EnableIA2"
future (and I am just making things up)
"filter object tree"
"limittovisiblearea"
Rich
It may be less performant but it is more flexible and gets rid of
versioning problems down the road.
> 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
