Re: [g-a-devel] Trying to understand STATE_SENSITIVE
- From: Aaron Leventhal <aaronlev moonset net>
- To: Willie Walker <William Walker Sun COM>
- Cc: g-a-devel <gnome-accessibility-devel gnome org>
- Subject: Re: [g-a-devel] Trying to understand STATE_SENSITIVE
- Date: Fri, 19 Jan 2007 10:42:21 -0500
If sensitive is True the widget will be sensitive and the user can interact with it. An insensitive
widget appears "grayed out" and the user can't interact with it.
/*Insensitive widgets are known as "inactive", "disabled", or "ghosted" in some other toolkits.*/
There you have it. Sensitive means not disabled. XForms calls that "relevant". MSAA/IA2 uses the opposite and calls it STATE_SYSTEM_UNAVAILABLE. In any case, SENSITIVE is the exact opposite of MSAA/IA2 STATE_UNAVAILABLE (aka disabled).
IMO, the main cause for confusion is that the use of the word
'enabled' in the AT-SPI and how its meaning there differs from how
enabled might be used in other toolkits.
Okay, but how is it being used in the API? What does ENABLED add to
SENSITIVE?
- Aaron
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]