GNOME Bugzilla – Bug 339021
nSelectedRows and nSelectedColumns not implemented
Last modified: 2006-06-09 16:56:49 UTC
Please describe the problem: Use of the Table::nSelectedRows and Table::nSelectedColumns properties via Python raises CORBA.NO_IMPLEMENT error. The at-spi documentation makes it sound like not all tables support row/column selection so it is possible that the NO_IMPLEMENT error is indicating that a particular table doesn't support this kind of information. However, this method of indicating the lack of row/column select support is inconsistent with what getSelectedRows() and getSelectedColumns() do. Those two methods return an empty list when row/column selection isn't supported instead of raising NO_IMPLEMENT. Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
Interesting. You are right in saying that there seems to be no implementation at all in libspi for these attributes. Certainly that should be fixed (one would expect '0' to be returned for table instances where row/column selection is not available). Note that there is no corresponding ATK property or method for getting the number of rows/columns selected; there are only methods which return the whole list. This may imply a performance penalty for clients which call 'get_nSelectedRows' before calling 'getSelectedRows'. Maybe we should deprecate these properties instead?
Fixed in CVS.
What was the fix? Deprecation or implementation? I can't think of a good use case for nSelectedRows and nSelectedColumns. The AT can just use getSelected* and count the results on its own if there is no optimization in the bridge.