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
when in a word document, navigation throughout a document with the braille display is slow #4995
Comments
Comment 1 by dkager on 2015-04-25 20:45 My only observation is that panning left/right within the same line is very fast but anything that moves the cursor to another line takes 250-500 ms. The delay is constant, I'm just not good at estimating. A few things that cause this cursor movement:
|
Comment 2 by jteh on 2015-04-26 02:36 We might be able to tighten this up with some caching, but there are always going to be performance problems here because of the way we have to get information from Word. Switching to UIA for Word will probably improve this, but aside from being a complete rewrite, that'll only work for Word 2013 and later. |
Any ideas on what in particular could be cached? |
I wonder whether braille.TextInfoRegion.update could be of negative impact here. A major drawback of that code is that it fetches textInfo text with fields in multiple runs. First, it gets the fields before the cursor/selection, then the selection/cursor itself, and then the fields for the text after the cursor/selection. This means that in the best case, getTextWithFields is called twice. This means that NVDA calls to word twice, gets several infos (including paragraph info twice), and even the info that isn't shown in braille at all. I think that there are some ways this can be improved:
Any other ideas? @jcsteh: what do you think about these? |
@leonardder commented on 4 Jun 2019, 20:11 CEST:
|
All of these ideas have merit. I don't think we've considered the filtering
idea before (and that could be a nice quick win), but we've definitely
discussed the other two.
With regard to the fields including selection start/end and caret, this
would require significant work/rewrites, as you say. However, it may be
really tricky for some implementations. For offset based implementations,
it's not so hard because you can map the offset of the caret, etc. directly
to an offset in the string. For implementations that aren't offset based,
though, it gets really messy: the underlying positions are opaque, and even
if there is some call to get the number of characters between two points,
you can't assume that a character and an offset are the same thing. For
those cases, you're probably going to end up having to internally fetch the
fields in three chunks anyway, although you might be able to make some
optimisations because you know you're going to do that.
|
I am using braille only very occasionally when working with LaTeX documents, so I cannot comment here unfortunatelly. |
@zstanecic are you still having this issue with NVDA 2023.1 RC1 and last build versions of Microsoft Word? |
Hi, |
@ABuffEr that's interesting. Just a short note that this setting is actually disabled by default. @LeonarddeR sorry I've totally missed your cc here, I had some other projects during last years so I could test your prototype now. Could you please rebase it on the last alpha version of NVDA? |
Does anyone see further performance issues with a braille display in NVDA 2023.2? Now my braille display is unfortunately broken, but tested some weeks ago and noticed a significant improvement. |
I've had fewer opportunities to use Word recently, but I just tried it with the 2021 version (16.0.16731.20234) and with UIA enabled, the performance seems good to me in several hundred-page documents. NVDA version: alpha-29194,ec914517 |
@aaclause what about performance when UIA is disabled? |
@burmancomp could you provide an update on NVDA performance in MS Word with UIA disabled in NVDA last alpha / advanced settings? |
With quick testing: If I use UIA always (but note that my system is w10 2022h2), braille scrolls rapidly. When using other UIA settings scrolling is slow. If I however enable "read by paragraph" when UIA is not "always", scrolling feels faster (I mean text seems to change on braille line faster when pressing and holding down braille next line button). |
Reported by zstanecic on 2015-03-24 13:57
steps to reproduce:
Press the navigation keys on your braille display. you should use up / down arrow keys simulation and scrolling keys..
After that, you will notice an one second lag..
It's present in latest snaps and in the stable 2015.1.
The text was updated successfully, but these errors were encountered: