Not sure in which situation a text object can have neither a single line nor multiple lines of text. These properties seem like complementary and mutually exclusive, in which case one bit would be enough. i.e., 0 = single line, 1 = multiple lines. Having said that, it is not a showstopper to keep both constants.
--Andres. > -----Original Message----- > From: [email protected] > [mailto:[email protected]] > On Behalf Of Alexander Surkov > Sent: Thursday, July 23, 2009 6:26 PM > To: James Teh > Cc: [email protected] > Subject: Re: [Accessibility-ia2] multi_line vs. single_line states > > I think the point is accessible can have state single line or multi > like or neither of them. It's like readonly and editable states. > Otherwise you should belong on role or something else to know > accessible is single or multi line (depending on what you're going to > remove). It's all assumptions. So it might be reasonable to save these > states both I think. > > Alex. > > > On Fri, Jul 24, 2009 at 6:19 AM, James Teh<[email protected]> wrote: > > On 24/07/2009 12:13 AM, Andres Gonzalez wrote: > >> Currently we have these two states: > >> /** Indicates this text object can contain multiple lines > of text. */ > >> IA2_STATE_MULTI_LINE = 0x200, > >> /** Indicates that this text object can contain only a > single line of > >> text. */ > >> IA2_STATE_SINGLE_LINE = 0x2000, > > Wow. I've never actually seen that SINGLE_LINE state! :) > > > >> Is there a reason why we need both constants? I'd rather > default to one > >> state (say, single_line) and make the other one explicit, > similar to > >> checked/unchecked or focused/unfocused. Having both seems > like a waste > >> of a precious bit in the states enum. Any body opposes > eliminating one > >> of these two constants? > > For what it's worth, NVDA doesn't use SINGLE_LINE. If we're > going to get > > rid of one, my vote would be to eliminate SINGLE_LINE. > > > > Jamie > > > > -- > > James Teh > > Email/MSN Messenger/Jabber: [email protected] > > Web site: http://www.jantrid.net/ > > _______________________________________________ > > 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 > _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
