Hello Glen, Thank you for your message. Before I add the customised scripts, I tried to use the pass key through feature with insert 3 and used CTRL up and down arrow when typing a command in the console window. However, the focus does not switch at all. It remains on the command history. Also, looking at the visual studio scripts in the script manager, I see there are a fair few scripts; would deleting all these not affect anything? Thank you, Chamandeep Singh Grover On 5/29/17, Glen Gordon wrote:

Hi,

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.

Let me know if you have problems.

--Glen

Glen Gordon VFO | Vice President & Chief Technology Officer 11800 31st Court North, St. Petersburg, FL 33716 T 727-299-6230 ggordon@vfo-group.com www.vfo-group.com

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Chamandeep Singh Grover via Blind-sysadmins Sent: Monday, May 29, 2017 10:15 AM To: program-l ; blind-sysadmins@lists.hodgsonfamily.org; raspberry-vi-request@freelists.org Cc: Chamandeep Singh Grover Subject: [Blind-sysadmins] visual studio 2015 enterprise, reading package manager console window with Jaws v18.

Hi All, I am following an online tutorial, which seems to use the package manager console quite a bit. When I go to the console, I can see my inputs, but not sure how to read the output window and confirm whether my command has been excecuted successfully? The only way I can read some of this is using the touch cursor and navigating to the text output section. But this is not efficient at all as I have to hear a lot of useless information before getting to the actual data. I don't know how much this will be required later on, but so far it is to enable migrations and to add migrations.

Thanks for any help you can give.

Regards, Chamandeep Singh Grover

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

Hi, Just tried this again with 2015. Opened PPM console Typed the word fred and pressed enter. Using Pass Key Through followed by Ctrl+UpArrow and then by Insert+UpArrow to read the lines did indeed navigate up past the error message that was shown in response to my invalid command. On your question about it being okay to delete the existing script content, the background is that JAWS ships with all scripts stored in its programdata folder. These are considered to be shared scripts and so an individual user is not allowed to edit them. When you go to edit one of these, JAWS makes a copy of the file from the programdata shared folder and puts it in your per-user JAWS settings directory. This means that subsequent updates to the shared scripts will be ignored when you're running JAWS because it will use your local copy instead. This has turned out not to be the best idea. Having your local script file just contain the additional/modified scripts, with the "use" line at the top gives you the best of both worlds. The new scripts you've added but the ability to benefit from any changes introduced to the shared scripts in the future. The use line says to JAWS: After you've loaded my personal scripts for this app, look for additional scripts by the same name that don't live in the same location where I loaded the scripts containing the "use" line. This causes JAWS to look in programdata. --Glen Glen Gordon VFO | Vice President & Chief Technology Officer 11800 31st Court North, St. Petersburg, FL 33716 T 727-299-6230 ggordon@vfo-group.com www.vfo-group.com -----Original Message----- From: Chamandeep Singh Grover [mailto:cmusic789@googlemail.com] Sent: Monday, May 29, 2017 2:29 PM To: Glen Gordon Cc: Blind sysadmins list ; program-l ; raspberry-vi-request@freelists.org Subject: Re: [Blind-sysadmins] visual studio 2015 enterprise, reading package manager console window with Jaws v18. Hello Glen, Thank you for your message. Before I add the customised scripts, I tried to use the pass key through feature with insert 3 and used CTRL up and down arrow when typing a command in the console window. However, the focus does not switch at all. It remains on the command history. Also, looking at the visual studio scripts in the script manager, I see there are a fair few scripts; would deleting all these not affect anything? Thank you, Chamandeep Singh Grover On 5/29/17, Glen Gordon wrote:

Hi,

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.

Let me know if you have problems.

--Glen

Glen Gordon VFO | Vice President & Chief Technology Officer 11800 31st Court North, St. Petersburg, FL 33716 T 727-299-6230 ggordon@vfo-group.com www.vfo-group.com

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Chamandeep Singh Grover via Blind-sysadmins Sent: Monday, May 29, 2017 10:15 AM To: program-l ; blind-sysadmins@lists.hodgsonfamily.org; raspberry-vi-request@freelists.org Cc: Chamandeep Singh Grover Subject: [Blind-sysadmins] visual studio 2015 enterprise, reading package manager console window with Jaws v18.

Hi All, I am following an online tutorial, which seems to use the package manager console quite a bit. When I go to the console, I can see my inputs, but not sure how to read the output window and confirm whether my command has been excecuted successfully? The only way I can read some of this is using the touch cursor and navigating to the text output section. But this is not efficient at all as I have to hear a lot of useless information before getting to the actual data. I don't know how much this will be required later on, but so far it is to enable migrations and to add migrations.

Thanks for any help you can give.

Regards, Chamandeep Singh Grover

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

Glen, Thank you - When I tried earlier, I was missing the sayLine command. your method indeed does work. Although I wish there was a cleaner way to review the output window and easy way to identify what windows you have open within VS and close them. The background about the customised scripts is very useful to know. Perhaps VFO would consider a webinar on visual studio and some tips and hints to navigate the development environment? Finally, is there an official channel where new features for VFO products can be suggested and considered by the relevant members within the VFO group? Thank you for your assistance - very much appreciated. Kind regards, Chamandeep singh Grover On 5/29/17, Glen Gordon wrote:

Hi,

Just tried this again with 2015. Opened PPM console Typed the word fred and pressed enter. Using Pass Key Through followed by Ctrl+UpArrow and then by Insert+UpArrow to read the lines did indeed navigate up past the error message that was shown in response to my invalid command.

On your question about it being okay to delete the existing script content, the background is that JAWS ships with all scripts stored in its programdata folder. These are considered to be shared scripts and so an individual user is not allowed to edit them. When you go to edit one of these, JAWS makes a copy of the file from the programdata shared folder and puts it in your per-user JAWS settings directory. This means that subsequent updates to the shared scripts will be ignored when you're running JAWS because it will use your local copy instead. This has turned out not to be the best idea.

Having your local script file just contain the additional/modified scripts, with the "use" line at the top gives you the best of both worlds. The new scripts you've added but the ability to benefit from any changes introduced to the shared scripts in the future. The use line says to JAWS: After you've loaded my personal scripts for this app, look for additional scripts by the same name that don't live in the same location where I loaded the scripts containing the "use" line. This causes JAWS to look in programdata.

--Glen

Glen Gordon VFO | Vice President & Chief Technology Officer 11800 31st Court North, St. Petersburg, FL 33716 T 727-299-6230 ggordon@vfo-group.com www.vfo-group.com

-----Original Message----- From: Chamandeep Singh Grover [mailto:cmusic789@googlemail.com] Sent: Monday, May 29, 2017 2:29 PM To: Glen Gordon Cc: Blind sysadmins list ; program-l ; raspberry-vi-request@freelists.org Subject: Re: [Blind-sysadmins] visual studio 2015 enterprise, reading package manager console window with Jaws v18.

Hello Glen, Thank you for your message. Before I add the customised scripts, I tried to use the pass key through feature with insert 3 and used CTRL up and down arrow when typing a command in the console window. However, the focus does not switch at all. It remains on the command history.

Also, looking at the visual studio scripts in the script manager, I see there are a fair few scripts; would deleting all these not affect anything?

Thank you, Chamandeep Singh Grover

On 5/29/17, Glen Gordon wrote:

...

Hi,

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.

Let me know if you have problems.

--Glen

Glen Gordon VFO | Vice President & Chief Technology Officer 11800 31st Court North, St. Petersburg, FL 33716 T 727-299-6230 ggordon@vfo-group.com www.vfo-group.com

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Chamandeep Singh Grover via Blind-sysadmins Sent: Monday, May 29, 2017 10:15 AM To: program-l ; blind-sysadmins@lists.hodgsonfamily.org; raspberry-vi-request@freelists.org Cc: Chamandeep Singh Grover Subject: [Blind-sysadmins] visual studio 2015 enterprise, reading package manager console window with Jaws v18.

Hi All, I am following an online tutorial, which seems to use the package manager console quite a bit. When I go to the console, I can see my inputs, but not sure how to read the output window and confirm whether my command has been excecuted successfully? The only way I can read some of this is using the touch cursor and navigating to the text output section. But this is not efficient at all as I have to hear a lot of useless information before getting to the actual data. I don't know how much this will be required later on, but so far it is to enable migrations and to add migrations.

Thanks for any help you can give.

Regards, Chamandeep Singh Grover

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

That's the plan but I can't give you an exact time. --Glen Glen Gordon VFO | Vice President & Chief Technology Officer 11800 31st Court North, St. Petersburg, FL 33716 T 727-299-6230 ggordon@vfo-group.com www.vfo-group.com -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Isaac Sent: Monday, May 29, 2017 4:41 PM To: Blind sysadmins list ; program-l ; raspberry-vi-request@freelists.org Subject: Re: [Blind-sysadmins] visual studio 2015 enterprise, reading package manager console window with Jaws v18. so why aren't these automatically implemented for jaws and visual studio ----- Original Message ----- From: "Glen Gordon" To: "Blind sysadmins list" ; "program-l" ; Sent: Monday, May 29, 2017 11:52 AM Subject: Re: [Blind-sysadmins] visual studio 2015 enterprise, reading package manager console window with Jaws v18.

Hi,

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.

Let me know if you have problems.

--Glen

Glen Gordon VFO | Vice President & Chief Technology Officer 11800 31st Court North, St. Petersburg, FL 33716 T 727-299-6230 ggordon@vfo-group.com www.vfo-group.com

-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Chamandeep Singh Grover via Blind-sysadmins Sent: Monday, May 29, 2017 10:15 AM To: program-l ; blind-sysadmins@lists.hodgsonfamily.org; raspberry-vi-request@freelists.org Cc: Chamandeep Singh Grover Subject: [Blind-sysadmins] visual studio 2015 enterprise, reading package manager console window with Jaws v18.

Hi All, I am following an online tutorial, which seems to use the package manager console quite a bit. When I go to the console, I can see my inputs, but not sure how to read the output window and confirm whether my command has been excecuted successfully? The only way I can read some of this is using the touch cursor and navigating to the text output section. But this is not efficient at all as I have to hear a lot of useless information before getting to the actual data. I don't know how much this will be required later on, but so far it is to enable migrations and to add migrations.

Thanks for any help you can give.

Regards, Chamandeep Singh Grover

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins

_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins