2 Dec 2011 05:39
Re: Extending GtkMenuItemAccessible to allow applications to set alternative accessible names for menu items.
Alexander Surkov <surkov.alexander <at> gmail.com>
2011-12-02 04:39:22 GMT
2011-12-02 04:39:22 GMT
Doesn't UI provide a tooltip in this case which is usually mapped to accessible name if name is not provided? At least that happens on the web. But technically it's sort of weird that application creates a widget but it can't control the properties of widget accessible object. Thanks. Alex. On Fri, Dec 2, 2011 at 10:32 AM, Luke Yelavich <luke.yelavich <at> canonical.com> wrote: > Hi all, > One feature request that the Ubuntu accessibility team receives from users, is the ability to find out the signal strength and security of a wireless network that appears in the network list. In the case of network-manager, the icon is used to convey network signal strength and security to the user. After looking through the code of GtkMenuItem, and GtkMenuItemAccessible, I've determined that there is currently no way to set an alternative accessible name for a menu item, in the case where the icon is conveying extra information to the user. Yes, one could put sed information in the label, but that would bloat the menu item visually, which is not desired. > > I was talking to a few GTK developers on IRC earlier today about GtkMenuItem, GtkMenuItemAccessible, and somehow allowing applications to set alternative accessible names for menu items, whether it be via an extension to the GtkMenuItem API, or extending the GtkMenuItemAccessible object to allow applications to set a different accessible name using the atk_object_set_name method call. Benjamin did suggest that the icon could possibly be exposed via another atk object which is a child of the menu item, with a description set in the icon atk object to describe the icon, however this gets messy when submenus are put into the picture. > > I'll let Benjamin et al reply as to what their thoughts are about this proposal, but I'd be interested in(Continue reading)
> over 10,000 lines (yes ten thousand!!!) of
> object:property-change:accessible-name getting queued up. One line
> per event. In other words, this is an epic event flood from
> Thunderbird or Gecko. I'm really not sure what I can do other than
> to ask Thunderbird/Gecko to just cut it out for pete's sake.
Well, that's simple, thunderbird can just not tell you about the
messages
More seriously the way a email client works is you have a treeviewish
thing with a list of all your messages (in this case ~25000). Each item
in the list view should be an accessible right? so we need to add each
of those 2500 accessibles, and then tell at-spi that each of them got a
name. I'm not sure why its 10000+ instead of 2500+ but that's roughly a
factor of four so with 0 debuging involved I'll gues there is more than
one accessible per message.
SO while I understand not wanting that many events I think you want
RSS Feed