You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: