To be honest, you’ve run into one of the oldest problems that Visual Studio
has… legacy keyboard shortcuts. There are only so many keyboard shortcuts we
can realistically make available and changing an existing keyboard shortcut
means changing the workflow for people who have gotten used to that existing
shortcut.
For example, Ctrl+P is still mapped to Print. I’ve been wanting to reclaim that
keyboard shortcut for quite a while now, but we still have hundreds of users
using that keyboard shortcut every month. If we change it, we know it’s going
to mess with the workflow of those users.
So, while features like “Next Method” or “Previous Method” might be useful,
it’s hard for us to know which methods are the “most” useful. I would LOVE to
find an easier way for folks to discover more useful commands and have an
easier way to bind them. As it stands right now, you can’t even use Ctrl+Q to
search for “Next Method” since it’s not bound to a command in any menu or
toolbar… so the ONLY way you can find it is with the Keyboard page in
Tools\Options.
If there are types of navigation you can’t find, please let me know and I’ll
see if they don’t exist (i.e., the command doesn’t exist at all) or if they
exist, but the name of the command is sufficiently esoteric that it’s not easy
enough to identify.
You also asked about navigating through issues in your document. Alt+PgUp and
Alt+PgDown will navigate through issues in your document. In the Error List,
there are toggles for Errors, Warnings and Messages. Alt+PgUp and Alt+PgDown
will navigate through all the issues that are shown based on those filters… so
if those filters are filtering out messages, then Alt+PgUp/Down should skip
over messages. You can get to those filters if you put focus on the Error List,
hit the Up arrow key until you get to the header of the Error table, then keep
hitting Shift+Tab until you find the filters. (For me, they report themselves
as Buttons, but they do identify as toggleable, so be aware that they don’t
identify themselves as checkboxes).
I hope this helps!
--Dante
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Tony Malykh
Sent: Thursday, November 24, 2022 9:01 PM
To: program-l@xxxxxxxxxxxxx; timothyjb310@xxxxxxxxx
Subject: [program-l] Re: Navigating with Visual Studio
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<mailto: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
