How much of a churn would it be to add a new state constant? We could
do a minor release, i.e. from 1.2 to 1.2.1 to add that constant.
--
*Pete Brunet*
a11ysoft - Accessibility Architecture and Development
(512) 238-6967 (work), (512) 689-4155 (cell)
Skype: pete.brunet
IM: ptbrunet (AOL, Google), [email protected] (MSN)
http://www.a11ysoft.com/about/
Ionosphere: WS4G
Richard Schwerdtfeger wrote:
>
>
>
> Rich Schwerdtfeger
> CTO Accessibility Software Group
>
> [email protected] wrote on
> 11/18/2010 04:29:54 PM:
>
> > From: James Teh <[email protected]>
> > To: IAccessible2 mailing list
> <[email protected]>
> > Date: 11/18/2010 04:31 PM
> > Subject: Re: [Accessibility-ia2] IA2_STATE_PINNED
> > Sent by: [email protected]
> >
> > On 19/11/2010 8:18 AM, Richard Schwerdtfeger wrote:
> > > For a state you have to run the IDL again. I am not arguing that we
> > > should not provide a provision for pinned but I would like to
> avoid the
> > > churn.
> > Makes sense. I'd be happy to support it as an object attribute if it is
> > endorsed by the IA2 spec. That said, it sets a precedent we may not
> want
> > to set; i.e. that all new states will become object attributes. Among
> > other things, this adds to the many object attributes that already
> > exist, and since there's no way yet to retrieve specific object
> > attributes, this is going to get very nasty sooner or later.
> >
> I understand. I also would like it to be endorsed by the IA2 spec too.
> All these attributes need to be documented.
>
> > 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
