Re: Excel Macro editing
Chris,
Yes, I have experienced it on all versions of Office from 2003 up to 2016. I am now working with 2016. I think it is time to raise an issue on GitHub, certainly.
All the best,
Cearbhall
m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...
Sent: Saturday, October 28, 2017 12:08 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Excel Macro editing
Hi Cearbhall
You do the same as me then. It’s really frustrating, Jaws works fine but I’ve got so much into NVDA I havenn’t even bothered to load the Jaws demo onto my machine. What version of Excel do you use? I’m on Excel 2007, if it affects more than my version, do you think it is worth raising it as an NVDA issue? I know the developers have recently improved many aspects of Excel functionality, if it is a common issue across different versions, it may be worth asking NVDA developers to have a look at our problems and as VBA macros extend across multiple Office products, it might kill multiple birds with one stone so to speak.
Cheers
Chris
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Cearbhall O'Meadhra
Sent: 27 October 2017 19:00
To: nvda@nvda.groups.io
Subject: Re: [nvda] Excel Macro editing
Hi,
NVDA is very poor when editing a macro in the edit screen. Pressing up-arrow from line to line can lose the focus on whole segments of code. Sometimes pressing “Code” on the edit menu in the macro editor improves the focus but not always. I normally highlight all the code and copy it into notepad where I can edit it fully. I then copy the edited version back into the macro editor, replacing the original code.
All the best,
Cearbhall
m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Thursday, October 26, 2017 11:59 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Excel Macro editing
I must admit I don't do a lot of VBA / macro editing currently, but with missing characters, check your symbol level. Many characters aren't read at lower symbol levels, which works great when reading web pages and e-mails, and not so great for code. You may like to set symbol level to all for working in VB - either with a configuration profile, or with the NVDA+p keystroke.
I can't reproduce missing lines just at the moment (I appreciate you said randomly), so will have to keep looking for that.
Regards
Quentin.
On Fri, Oct 27, 2017 at 4:30 AM, Chris Mullins <cjmullins29@...> wrote:
Hi
Using W10 Home, NVDA 17.3 ms Excel 2007.
There have been long-standing issues where NVDA does not work properly when editing macro VBA code and cell formulae in Excel 2007. When navigating VBA code line by line with arrow keys, NVDA will randomly miss out speaking lines of code and when editing formulae, it will randomly miss out voicing some characters, occasionally saying space instead, when using the arrow keys to move character by character. Has anyone had these issues and found any solutions, maybe in later Excel versions?
Cheers
Chris
--
Quentin Christensen
Training and Support Manager
Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess