GNOME Bugzilla – Bug 419136
[pending] Planner toggle button in main window not accessible
Last modified: 2008-07-22 19:33:42 UTC
This is a tracking bug for bug 337382. The problem is that planner should use the LABEL_FOR relationship to match up each toggle button with the appropriate label.
Removing target milestone from [blocked] bugs. We have little control over them, so we're better off letting priority and severity be our guide for poking the related components.
Created attachment 104979 [details] [review] Revision #1 This is the patch we will have to apply to the planner.py script when bug #337382 is fixed.
Removing the "[blocked]" as the underlying bug has been fixed.
Given the information that Orca's planner script no longer works well with the fixed planner functionality, please commit this patch for GNOME 2.21.92 (assuming you have tested it). Thanks!
Patch committed. Moving to "[pending]" state.
Still problems with this. The latest changes to planner.py for contracted braille are causing a traceback: Traceback (most recent call last):
+ Trace 188993
s.processObjectEvent(event)
self.listeners[key](event)
self.onFocus(event)
orca.setLocusOfFocus(event, newFocus)
orca_state.locusOfFocus)
newLocusOfFocus)
self.updateBraille(newLocusOfFocus)
braille.setFocus(result[1])
offset += _regionWithFocus.cursorOffset - _displaySize[0] + 1
We should be passing in a True or False as the third parameter to: componentRegion = braille.Component(obj, text, indicator) but indicator is: indicator=\ settings.brailleRadioButtonIndicators[brailleindicatorindex] and settings.brailleRadioButtonIndicators[brailleindicatorindex] is: brailleRadioButtonIndicators = ["& y", "&=y"]
It was a tiny issue that I fixed in trunk. A keyword for the argument was needed.
Verified. Thanks Eitan!