[program-l] Re: jaws and package manager console of visual studio 2017

  • From: Soronel Haetir <soronel.haetir@xxxxxxxxx>
  • To: program-l@xxxxxxxxxxxxx
  • Date: Mon, 11 Sep 2017 05:41:22 -0800

Note that the SayNextParagraph/SayPriorParagraph scripts are not bound
by default but that ControlDownArrow/ControlUpArrow are. So if you
don't want to mess with keyboard bindings you need to rename the
provided scripts.

On 9/7/17, Chamandeep Singh Grover <dmarc-noreply@xxxxxxxxxxxxx> wrote:

Hello,
Here is a response i received to this question earlier this year.
If you follow the steps below, the package manager console does become
very usable.
Hope it helps.

"Visual Studio has little known keystrokes Ctrl+DownArrow and
Ctrl+Uparrow that will let you move the caret into the output portion
of the PPM console window.
The regular up and down arrow keys keep you on the command line and
switch through command history.
Unfortunately, JAWS has the say next and say prior paragraph scrips
globally attached to Ctrl+DownArrow And Ctrl+UpArrow respectively.
This means that these keys currently do not work out of the box.
You can use Ctrl+3 to do a pass key through followed by SayLine but
that's not very efficient.

Do the following to add some scripts to accomplish what's needed:
Switch focus to Visual Studio.
Press Insert+F2 to bring up the list of JAWS managers.
Select Script Manager.
This should bring up Script Manager with a local copy of the VS scripts.
Do A select all and delete what's there.
Copy the following in it's place:

use "Visual Studio 2010.jsb"
script SayPriorParagraph()
        typekey("Ctrl+UpArrow")
        SayLine()
EndScript

Script SayNextParagraph()
        TypeKey("Ctrl+DownArrow")
        SayLine()
EndScript

Save/Compile with Ctrl+s.

The use line tells JAWS to use the shared scripts but then add the
following scripts as well.
This approach will ensure that these new custom scripts are always add
to what's used for VS even if they're changed in the next JAWS
update."
<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
      <tr>
        <td style="width: 55px; padding-top: 13px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail";
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif";
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
              <td style="width: 470px; padding-top: 12px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Virus-free. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail";
target="_blank" style="color: #4453ea;">www.avast.com</a>
              </td>
      </tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
height="1"></a></div>

On 9/7/17, Константин <galiahmetov@xxxxxxxxxx> wrote:
Hi guys
Please tell me how do you read package manager console output of visual
studio  2017 using jaws?
thank you so much!
** 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



-- 
Soronel Haetir
soronel.haetir@xxxxxxxxx
** 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

Other related posts: