* What is gnome-mag?
gnome-mag provides a command-line interface for standalone use,
although its primary goal is to provide a set of magnification
services for use by other client applications and assistive
technologies.
Download at the usual place :
ht
I see what you're saying. It looks like it should be SENSITIVE. For
example, let's take a GTK label. If it is not grayed, it is SENSITIVE.
Will
Peter Parente wrote:
>> In this case, the toolbar has the SENSITIVE state and is not grayed.
>
> Good. Now, look at a Firefox paragraph or other elem
> In this case, the toolbar has the SENSITIVE state and is not grayed.
Good. Now, look at a Firefox paragraph or other element inside a
webpage that is not interactive and compare it with an element that is
interactive but currently grayed.
Pete
On 3/2/07, Willie Walker <[EMAIL PROTECTED]> wrote
Thanks! These help. Let's focus on the SENSITIVE state as a means to
do what you want. I verified all these examples using at-poke.
> 1) The user tabs to the Close button in the gedit settings dialog. In
> this case, we might say the name of the button, the role of the
> button, and the mnemon
Sure. Here are examples representative of the three cases we want to
handle in LSR.
1) The user tabs to the Close button in the gedit settings dialog. In
this case, we might say the name of the button, the role of the
button, and the mnemonic for the button.
2) The user reviews to a grayed out me
Hi Peter:
> So how does Orca distinguish the case of some interactive widget being
> disabled from some widget that can never be enabled? Does Orca say
> disabled in both cases?
Can you enumerate some actual use cases? Concrete examples might make
this discussion easier.
Thanks!
Will
>> Of
Hi Will,
So how does Orca distinguish the case of some interactive widget being
disabled from some widget that can never be enabled? Does Orca say
disabled in both cases? Or, when you notice state sensitive is
missing, do you check again other information (e.g. list of roles that
could be enabled/
I would prefer to remain with what gail does; I view it as the reference
implementation of the AT-SPI. Changing the behavior of an established
meaning and implementation to accommodate a difference in a new API for
a different platform (IAccessible2) seems odd to me. It also seems like
someth
Aaron Leventhal wrote:
> Bill Haneman wrote:
>
>> My vote would be to retain FOCUSABLE when an object is greyed out, but
>> that could confuse clients who expect the object to remain in the focus
>> chain.
>>
>>
> First, thanks for your input on this. Not to muck things up, but I wou
