GNOME Bugzilla – Bug 423588
Tree view cells dead on arrival
Last modified: 2007-05-11 19:55:59 UTC
For example, when browsing the home directory in Nautilus in icon view mode, the "Name" column is not read out except for the first time the treeview cursor gets focus.
This must be a recent regression. My demo at CSUN involved browsing the Nautilus tree view with LSR. Everything was read fine.
Verified this works properly with Nautlius with LSR trunk. What version at-spi, atk, and nautilus do you have on your system?
*** Bug 423586 has been marked as a duplicate of this bug. ***
Verified again on a second FC6 machine that nautilus trees are read properly. Checked accerciser with LSR again. This is the exception I'm getting with LSR on the tree view in accerciser. Traceback (most recent call last):
+ Trace 122896
client(event)
eh.getAEEvents(event, self.event_manager.postEvents)
return func(self, *args, **kwargs)
events = method(event, focused=focused)
return (self._getSelectorEvent(event.any_data, event.detail1, **kwargs),)
if accessible.childCount > 0:
The TableAdapter seems to be getting an object that is not already an accessible. Perhaps an explicit queryInterface will help? Still odd.
Adding the lines: print accessible print type(accessible) just before the line throwing the exception above (line 444 in TableAdapter) yields the following output: [print Level 15 2007-03-28 09:05:35,594] [DEAD] [print Level 15 2007-03-28 09:05:35,594] <class 'Accessibility.Accessible'> So apparently we're getting objects, but they're dead on arrival.
If we request the Accessible interface on the objects in any_data when they arrive in pyLinAcc, the problem is resolved.
(In reply to comment #6) > If we request the Accessible interface on the objects in any_data when they > arrive in pyLinAcc, the problem is resolved. Not quite. The ref call is needed too. I'm changing pyLinAcc so that a ref is attempted on all any_data values. If it's an accessible, we'll correctly increase the reference count. If it's not, we catch the attribute error.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.