MS Word table navigation scripts rather slow #3326

Closed
nvaccessAuto opened this Issue Jul 3, 2013 · 4 comments

2 participants

@nvaccessAuto

Reported by mdcurran on 2013-07-03 05:01
Table navigation scripts in MS Word (control+alt+arrows) are rather slow, especially in large tables.
It looks like the calls to range.information to get row and column numbers is what takes the most time. In deed any call to range.information has always been bad, so we should strive not to use it where ever possible.
MS Word cell objects have rowIndex and columnIndex properties (2003 and up) which seem to be much faster, so these should be used instead.

@nvaccessAuto

Comment 1 by mdcurran on 2013-07-03 05:20
Try build here:
http://community.nvda-project.org/try/t3326/nvda_snapshot_try-t3326-9283,829adba.exe
I tested with Word 2010 and can test 2007, but need others to test on 2003 if possible.
The t3326 branch appart from not using range.information also improves the table movement algorithm some what to make less calls to Word and also fixes an issue when trying to move down a column with cells that span multiple rows.

@nvaccessAuto

Comment 2 by mdcurran on 2013-07-08 06:22
Incubating in 2def69a
Changes:
Added labels: incubating

@nvaccessAuto

Comment 3 by Michael Curran <mick@... on 2013-07-22 00:32
In [3b61417]:
```CommitTicketReference repository="" revision="3b61417e9730751eec454c1a7a9a02a2c5b4f468"
Merge branch 't3326' - Performance improvements when using table navigation commands in MS Word

Fixes #3326

Conflicts:
user_docs/en/changes.t2t

Changes:
Removed labels: incubating
State: closed
@nvaccessAuto

Comment 4 by mdcurran on 2013-07-22 03:41
Changes:
Milestone changed from next to 2013.2

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