Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement tableInfo property on NVDAObjects. #234

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 1 comment
Closed

Implement tableInfo property on NVDAObjects. #234

nvaccessAuto opened this issue Jan 1, 2010 · 1 comment
Assignees
@michaelDCurran
Labels
enhancement
Milestone
2009.1

Comments

@nvaccessAuto
Copy link

Reported by mdcurran on 2008-11-24 06:07
APIs such as Java Access Bridge, IAccessible2 and UI Automation provide information about tables and table cells on objects that represent these things. NVDA currently has no way of gathering or reporting this information.
A tableInfo property should be implemented on NVDAObjects, which will be a dictionary consisting of possible following values:
currentRowNumber, currentRowHeader, currentColumnNumber, currentColumnHeader, numberOfRows, numberOfColumns.
If this object is the actual table, then the 'current' values shouldn't exist. But if this object is a cell, then the 'current' values, and the 'numberOf' values should exist, for ease of use.
@nvaccessAuto
Copy link
Author

Comment 1 by mdcurran on 2009-02-16 02:27
properties of rowNumber, rowCount, columnNumber, columnCount, and table, have been implemented on NVDAObjects, in r2720. The tableInfo dict idea was not used as this would mean that all these properties would have to be reatreaved at the one time, and not all accessibility APIs would allow this.
Changes:
State: closed

@nvaccessAuto nvaccessAuto added this to the 2009.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelDCurran michaelDCurran

Labels
enhancement
Projects
None yet
Milestone
2009.1
Development

No branches or pull requests
2 participants
@michaelDCurran @nvaccessAuto