GNOME Bugzilla – Bug 342269
Dogtail lacks support for AccessibleValue instances
Last modified: 2011-02-07 06:05:00 UTC
Please describe the problem: Currently dogtail does not provide support for AccessibleValue. I filed a bug and a patch for this issue in Pyspi (it lacks support for this one too). The value interface is used for widgets that model a numeric value in a range (scrollbars, progressbars, ranges, spinbuttons and panes). Steps to reproduce: 1. Get a widget supporting AccessibleValue Actual results: AccessibleValue is not exposed through dogtail. Expected results: If we follow the standards for other interfaces, we could expose value as a private attribute of node. Then we can get minimumValue, maximumValue and currentValue as attributes. The last one read/write. Does this happen every time? Yes Other information:
Created attachment 65778 [details] [review] This patch adds support for AccessibleValue in dogtail This patch adds support for AccessibleValue in dogtail. It provides access to the AccessibleValue interface in Pyspi (see bug 342266 for a patch providing this support). It adds three attributes for nodes implementing AccessibleValue: * currentValue (read/write) * minimumValue (read-only) * maximumValue (read-only)
Patch looks good to me. Nitpicking: (i) looks like the setattr code will need to add some trivial logic to reject attempts to set the max/min value, raising a ReadOnlyError. (ii) do we like the names of these attributes? Could they be shorter e.g.: - value - maxValue - minValue ? Or do we prefer to have consistency with what ATSPI calls them?
I'd like to have AccessibleValue support in dogtail, but it's just a matter of having Dave's concerns (which I share) addressed. I don't currently have the time.
dogtail development has been stalled and it has been unmaintained for a few years now. Maintainers don't have future development plan so i am closing bugs as WONTFIX. Please feel free to reopen the bugs in future if anyone takes the responsibility for active development.