[program-l] Re: Navigating with Visual Studio

  • From: Tony Malykh <anton.malykh@xxxxxxxxx>
  • To: program-l@xxxxxxxxxxxxx, timothyjb310@xxxxxxxxx
  • Date: Thu, 24 Nov 2022 21:00:48 -0800

Re: jumping to methods, if you use NVDA, you can do this with my Tony's enhancements add-on. You can configure regexp of method definition in your language and bind it to keys like PrintScreen and Shift+PrintScreen.
Re: speaking line after keystroke: this is another feature of Tony's enhancements. I called it dynamic keystrokes - it can make NVDA to speak current line right after you press certain keystroke - keystroke can be configured.
And since I am already doing shameless self-promotion, you can also check out my IndentNav add-on. It allows to jump between lines with the same indentation, which would kinda allow you to jump between method definitions -  it would also stop on closing braces though.


On 11/24/2022 12:46 PM, timothyjb310@xxxxxxxxx wrote:


Hi all,

So I have been learning visual studio and C#. I had a couple of questions on keyboard navigation.

The first is about navigating in code by method. I did some digging and found how to assign a key stroke to next and previous method actions since in default visual studio they do not seem to be applied. I was also playing with the resharper bindings. One thing that I noticed is that neither NVDA or JAWS read the line that is navigated to. Is anyone familiar with this, and know of any addons to speak out the line that is navigated to?

My second question is about handling syntax errors. What is the best way to navigate through syntax errors? I know that I can do control+\ control+e to navigate to the errors window, however is there shortcuts for jumping to next/previous error in the editor and a way to view the error in the editor without leaving the editor?

I am curious also if there is any way to improve the intelligence screen reader output experience. It works well enough, although seems to lag and does not always seem to catch the cursor in the auto complete dropdown. This might just be a quirk of visual studio, although I found eclipse and visual studio code to respond a bit better than this.

Thanks,

Timothy Breitenfeldt

Other related posts: