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
Caret navigation problems when editing or browsing formulas in Excel #4537
Comments
Comment 3 by Palacee_hun on 2014-12-06 23:56 Changes: |
Comment 4 by mdcurran on 2014-12-11 06:01 |
Comment 5 by Palacee_hun on 2014-12-14 11:17 |
This issue was definitely present very starkly till November last year, after which my usage of Excel became negligible. In my brief testing with NVDA 2017.3 RC 1 and Excel 2010 on Windows 8.1 just now, when I type "=sum(a2:a3)" in A1, pressing F2 on A1 to read the formula syntax itself, NVDA misses out on the last character of the formula, i.e. ")". This is consistently reproducible because the ')' just isn't existent to NVDA although I have ensured its presence. Thoughts? @michaelDCurran |
After pressing F2, maximize the window.
That way, NVDA reports all characters...
Rui
…-----Mensagem Original-----
De: bhavyashah
Data: 18 de agosto de 2017 16:59
Para: nvaccess/nvda
Cc: Subscribed
Assunto: Re: [nvaccess/nvda] Caret navigation problems when editing or
browsing formulas in Excel (#4537)
This issue was definitely present very starkly till November last year,
after which my usage of Excel became negligible. In my brief testing with
NVDA 2017.3 RC 1 and Excel 2010 on Windows 8.1 just now, when I type
"=sum(a2:a3)" in A1, pressing F2 on A1 to read the formula syntax itself,
NVDA misses out on the last character of the formula, i.e. ")". This is
consistently reproducible because the ')' just isn't existent to NVDA
although I have ensured its presence. Thoughts? @michaelDCurran
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
The work-around mentioned by @ruifontes in #4537 (comment) does not make any change in the test I performed and described in #4537 (comment). The ")" remains invisible to NVDA even when Excel is maximized or object review is used to inspect the cell contents. |
Duplicate of #4372. However I suggest closing #4372 because the discussion here goes in more detail. cc: @LeonarddeR, @Qchristensen your thoughts are very apreciated. |
In Excel 365, I just get a slight slowdown when passing brackets, as per my comment on 4372, I just tried in Excel 2007, and in a new worksheet on A1, typed the formula =(B1 + C2)+D3 and as I move through the formula, it first read ok, but after that reads "space" for the character AFTER ( or ) when right arrowing, but when I left arrow back through the text, it reads "space" for both the character to the right of the ( or ) as well as the parenthesis itself. When it reads space, in the log I get the following entry: DEBUGWARNING - synthDrivers.sapi5.SynthDriver.speak (14:21:30.796): On Excel 2007 on Windows 7, it seems to work the same whether I have allow editing directly in-cells enabled or not. |
I decided to close this in favor of #4372 because that issue is being referenced on newer issues as well. |
Reported by Palacee_hun on 2014-10-08 13:53
It's not possible to give exact steps to reproduce, because this appears a bit randomly, but I can give a fair description.
When I arrow through a formula in order to edit it (after pressing F2), I experience that sometimes NVDA says "blank" or the character at the previous caret position instead of saying the correct character under the caret. This happens most often near parentheses in the formula. This makes formula editing quite unreliable and error-prone.
Symptoms make me think that the caret timeout is too small for formula editing in this edit box, because Excel does a lot of processing during editing formulas. I've never experienced this when doing simple data entry/editing.
This problem is reproducible with Jaws, although the symptoms are a bit different, but point to the same cause.
My machine is not particularly slow (1.8 Ghz, dual-core Intel CPU). I use Excel 2003, but this problem may well present itself with other versions.
Increasing the caret timeout for this edit box wouldn't do much harm, but it would most probably eliminate this problem.
The text was updated successfully, but these errors were encountered: