The notification crash is a known issue and so far as I know we're
still waiting on a fix.
On 10/20/18, Jordy Deweer <jordyydeweer@xxxxxxxxx> wrote:
Dear all
I have two issues with Visual Studio 2017 (Community).
The first problem is the following: when I work with the Team Explorer
(to manipulate Git), everything works fine, until I commited something.
After commiting, an extra part in the window appears, which ontains
notifications. If I press Tab to go back to the list of, for example,
unstaged items, I need to pass-by that notifications area. But, VS
crashes as soon as the notifications area gets the focus (using tab). Is
that a known problem, can it be resolved by a modification in the
settings, etc.? When tere are errors and I try to read the notifications
from the Team Explorer window, the first line goes well, but as soon as
I press one of the panning buttons on my Focus 40 Blue (4th Gen) braille
display, everything crashes as well, just like it does when tere are no
errors and the notifications box get the focus...
My second problem is that, when I am using JAWS 2018 to edit code, it
happens that the braille stays on the "mnu text editor" message of
IntelliSense, while I am back in the code itself with my focus. The
speech works fine though. I tried maximalizing the window, restarting
everything, but it did not resolve the problem. Hereby needs to be said
that it doesn't always happen. When I am in trouble, a simpel restart of
JAWS is enough to solve everything- until it happens again.
Is there a way to solve the above problems or will there need to be bug
fixes in Visual Studio?
Thanks in advance for possible replies.
Yours faithfully
Jordy Deweer
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
