Date   
Re: New windows not always detected

Dejan Ristic
 

I have encountered it, too.


On 2/25/2017 8:51 AM, Felix G. wrote:
Hello,
I'd like to ask if anyone else has encountered the following:
When launching an application, for example by hitting enter on Mozilla Firefox on the desktop, NVDA sometimes fails to detect there is a new active window. It will not automatically say anything, and pressing NVDA+t will still yield "Explorer" as if the desktop still had focus. However, pressing tab clearly shows that Firefox had focus because it performs the expected action of jumping, for example, out of the address field and into the search field.
For an experiment I gave it a full five minutes to see if it just takes an awful lot of time, but no luck. So, window activation events seem under certain conditions to be able to pass under NVDA's radar.
It might be worth noting that I noticed this not long after a reboot and the dust might not have fully settled in terms of background tasks starting and stopping.
Kind regards,
Felix


Virus-free. www.avast.com

Re: New windows not always detected

 

hi.
i use windows xp and dont have such problem.
i am not sure about other versions of windows.

On 2/25/17, Jacques <lists4js@...> wrote:
As previously reported, this scenario certainly is true for Office
applications too. I personally am hoping for an improvement in this regard
for the next release. However, I do have sympathy for the developers, since
it cannot be reproduced consistently.



Jacques



<https://www.stascom.co.za/> Open my home page |
<mailto:webmaster@...> contact webmaster |
<https://www.twitter.com/stassenj> follow on Twitter



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Felix
G.
Sent: Saturday, 25 February 2017 09:51
To: nvda@nvda.groups.io
Subject: [nvda] New windows not always detected



Hello,

I'd like to ask if anyone else has encountered the following:

When launching an application, for example by hitting enter on Mozilla
Firefox on the desktop, NVDA sometimes fails to detect there is a new active
window. It will not automatically say anything, and pressing NVDA+t will
still yield "Explorer" as if the desktop still had focus. However, pressing
tab clearly shows that Firefox had focus because it performs the expected
action of jumping, for example, out of the address field and into the search
field.

For an experiment I gave it a full five minutes to see if it just takes an
awful lot of time, but no luck. So, window activation events seem under
certain conditions to be able to pass under NVDA's radar.

It might be worth noting that I noticed this not long after a reboot and the
dust might not have fully settled in terms of background tasks starting and
stopping.

Kind regards,

Felix



--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org

Re: New windows not always detected

Jacques <lists4js@...>
 

As previously reported, this scenario certainly is true for Office applications too. I personally am hoping for an improvement in this regard for the next release. However, I do have sympathy for the developers, since it cannot be reproduced consistently.

 

Jacques

 

Open my home page  |  contact webmaster  |  follow on Twitter

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Felix G.
Sent: Saturday, 25 February 2017 09:51
To: nvda@nvda.groups.io
Subject: [nvda] New windows not always detected

 

Hello,

I'd like to ask if anyone else has encountered the following:

When launching an application, for example by hitting enter on Mozilla Firefox on the desktop, NVDA sometimes fails to detect there is a new active window. It will not automatically say anything, and pressing NVDA+t will still yield "Explorer" as if the desktop still had focus. However, pressing tab clearly shows that Firefox had focus because it performs the expected action of jumping, for example, out of the address field and into the search field.

For an experiment I gave it a full five minutes to see if it just takes an awful lot of time, but no luck. So, window activation events seem under certain conditions to be able to pass under NVDA's radar.

It might be worth noting that I noticed this not long after a reboot and the dust might not have fully settled in terms of background tasks starting and stopping.

Kind regards,

Felix

Re: getting NVDA to indicate capital letters

Gene
 

The trouble shooting procedures suggested in the below message are probably unnecessary.   The first thing to determine is whether this function is supported by the implementation of Eloquence being used.  this can be determined pretty accurately by switching to a different synthesizer such as e-speak and seeing whether the pitch change changes when the number is changed.  If it does, then this is likely something the user can't change with the implementation of Eloquence being used. 
 
With e-speak, the default 30 produces very little pitch change.  Using something as a test such as 60 produce a dramatic pitch change.
 
Gene

----- Original Message -----
Sent: Friday, February 24, 2017 11:54 PM
Subject: Re: [nvda] getting NVDA to indicate capital letters

That's kindly odd to know. I may asked what version of nvda that was installed to your machine? or perhaps tried to disable all the addons by restarting to double check the problem. I don't think any possible could have trigger a problem other than that because it works fine from here at all. Or, the last option will be resetting the nvda to factory default to ensure you made all the possible troubleshooting.

Robert Mendoza
On 2/25/2017 1:38 PM, Dennis L wrote:

I increased it but didn’t notice any difference

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Mendoza
Sent: Saturday, February 25, 2017 12:22 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

It seems you just increases the pitch volume of the voice itself. But, you were able to tabbed through till you heard that says "Capital pitch change percentage 30", The numeric or the edit field of 30 was the default You can increases it that the value on your preferred or desired value you like. Then, pressed Okay to take apply the changes.


Robert Mendoza

On 2/25/2017 11:37 AM, Dennis L wrote:

I tried that nothing happened. When I got to the setting I didn't notice a difference after making the number higher.

Sent from my Android phone using Aqua Mail

On February 24, 2017 10:31:05 PM "Robert Mendoza" <lowvisiontek@...> wrote:

You may pressed nvda plus control V, to go directly of the Voice Setting options. Then, follow the steps mentioned below as per suggested earlier to this thread.


Robert Mendoza

On 2/25/2017 10:38 AM, Dennis L wrote:

When I press nvda v nothing happens.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..

 

 


Re: New windows not always detected

Michael Capelle <mcapelle@...>
 

yes, this happens all the time on my 7 and 10 machine.
 

From: Felix G.
Sent: Saturday, February 25, 2017 1:51 AM
Subject: [nvda] New windows not always detected
 
Hello,
I'd like to ask if anyone else has encountered the following:
When launching an application, for example by hitting enter on Mozilla Firefox on the desktop, NVDA sometimes fails to detect there is a new active window. It will not automatically say anything, and pressing NVDA+t will still yield "Explorer" as if the desktop still had focus. However, pressing tab clearly shows that Firefox had focus because it performs the expected action of jumping, for example, out of the address field and into the search field.
For an experiment I gave it a full five minutes to see if it just takes an awful lot of time, but no luck. So, window activation events seem under certain conditions to be able to pass under NVDA's radar.
It might be worth noting that I noticed this not long after a reboot and the dust might not have fully settled in terms of background tasks starting and stopping.
Kind regards,
Felix

Re: Questions and suggestions

Gene
 

For years, the only way blind people could get to the system tray was with the screen-reader dialog.  It became so well entrenched and so expected a way to reach it that it should be included in screen-readers.  Whether it is duplicative or not, at times in this and other contexts, technology related or not, a practice is so well entrenched that it may be desirable to continue it whether it is duplicative or not. 
 
Sighted people have constant and unnecessary instructions on how to do things.  How many obvious buttons on machines, for example, have something completely unnecessary written as a prompt such as push.  What else are you going to do with a button on a machine? Why is there so much opposition to, not as a general practice, but in this one instance, making things a gbit easier for a lot of NVDA users while doing no harm? 
 
And at very rare times, I have found it necessary to have the dialog available.  As I said yesterday, I've seen very rare instances where you can't work with an icon except in the screen-reader provided system tray dialog.
 
Furthermore, to work with the Windows implementation, you need to know commands most blind computer users don't know.  Enter equals left double click in the system tray.  Space bar equals left single click.  The context menu key equals right click.  Since even a lot of experienced computer users don't know such commands implementing a system tray dialog will eliminate frustration and problems that will occur without knowing them.  And, unless this has been changed, these commands are not covered in the NVDA users' guide.  And how many people read manuals with any thoroughness?  And finally, when using the system tray directly, you don't up and down arrow through icons.  You right or left arrow.  The commands I've given and the difference in movement commands can easily be explained.  But most users are not on lists such as this, probably don't read the user Guide with the kind of thoroughness that would allow them to discover such commands and, as I said, unless this has changed, these things aren't discussed in the users Guide.  The Windows command is given at some point, but I don't think any of what I have discussed other than that is provided. 
 
Gene
----- Original Message -----

Sent: Friday, February 24, 2017 9:35 PM
Subject: Re: [nvda] Questions and suggestions

This argument is silly.

The windows-b key gives you access, what's the issue?  Windows-b works regardless of screen reader, windows version, or desktop/laptop keyboard layout.  I see no problem here, and arguing that other screen readers provide another keystroke for the same function is a spurious argument.  Other windows screen readers aren't open source either, but I don't see anyone pushing to have this fixed.  Other windows screen readers also tend to be larger, and take up more system resources (on average) but I don't see anyone complaining about this either.  Just because other screen readers have something doesn't automatically make it something NVDA *must* have.  Windows provides the keystroke windows-b for a reason, and there's no reason to duplicate the effort by building access to the same function just because you can.

Good lord, if folks wanted every single windows function duplicated, just imagine how much bloat screen readers would have.  Nothing wrong with leaving windows keystrokes alone, and just pointing them out when someone asks.  No need to needlessly duplicate existing functionality.  Should NVDA provide another keystroke to switch between programs when alt-tab does the job just fine?

Give it a rest already.



On 2/24/2017 5:34 PM, Kwork wrote:
Agreed here completely. This should be a core NVDA function, and not only available by installing an add-on. But this has been hashed out before, with NVDA developers ignoring the desires of some of us users.
Travis
----- Original Message -----
From: Gene
Sent: Thursday, February 23, 2017 10:29 PM
Subject: Re: [nvda] Questions and suggestions

That isn't the reason and that argument is irrelevant.  The system tray wasn't accessible years ago through Windows.  There needed to be a screen-reader dialog to provide access.  That's how the whole separate access got started and System Access uses the same command.  Window-eyes uses a different command but it too provides a system tray dialog. 
 
There are times, like it or not, when the dialog works better than using the Windows access method and it should be provided as a part of screen-readers. 
 
Sometimes, I get access to something using the Windows method when the dialog doesn't work properly and at other times, I have found the only way I've gotten access to an item is by using the dialog.  These instances where one or the other method doesn't work are rare but the argument that the screen-reader dialog method is nothing but duplication is not correct. 
Gene
----- Original Message -----
Sent: Thursday, February 23, 2017 10:21 PM
Subject: Re: [nvda] Questions and suggestions

Because NVDA is not jaws, and there's no reason to make it mirror jaws keystrokes.  The windows-b keystroke will work no matter what you use for a screen reader, since it's a windows command.  That's why NVDA uses it.  There is no dedicated NVDA keystroke for this function.



On 2/23/2017 8:36 PM, Arlene wrote:

Hi, I don’t know if I can say here! When you go to your system trey. Why not make future builds of NVDA be insert F 11? Instead of windows B. 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Damien Sykes-Lindley
Sent: February-23-17 9:06 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Questions and suggestions

 

Hi Gene,

Hotkeys are indeed excellent. One of the first thing I look for in a program is hotkeys. In fact, some have so many that it’s hard to memorise all of them. But at least they’re there!

The only problem I have with Windows shortcuts being linked to them is that, because they are global throughout the whole system, it can unfortunately cause conflicts with other running applications that utilise those shortcuts. For instance, I could assign a ctrl+alt+q shortcut to launch QWS (a MIDI sequencer), and another application may use ctrl+alt+q to mean quit. I have known ctrl+alt+o for options, ctrl+alt+x for exit, ctrl+alt+n/p for next/previous, all of which can be assigned to a Windows hotkey, and then it’s touch and go as to which item activates. Otherwise, I’m definitely all for hotkeys!

As an aside, I must admit I do find it odd, and mildly frustrating that there are four modifier keys that can be used to register hotkeys and yet it is still possible to run out of logical keys! This is even more so for global shortcut-linked ones, since I think you can only have ctrl+alt and ctrl+shift combos. Possibly if you’re extremely dextrous you might be able to have ctrl+shift+alt, I haven’t dared to try that one. Lol.

First letter navigation. Now you mention it I am aware of it. I use it all the time to move quickly to files in Explorer. But for some reason it didn’t cross my mind for the desktop (even though I know that is also controlled by explorer). I guess because my explorer is in detail view, and the desktop shows as a sort of grid layout I treated them as two separate systems. Strange how brains work!

Cheers.
Damien.





Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com






Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


New windows not always detected

Felix G.
 

Hello,
I'd like to ask if anyone else has encountered the following:
When launching an application, for example by hitting enter on Mozilla Firefox on the desktop, NVDA sometimes fails to detect there is a new active window. It will not automatically say anything, and pressing NVDA+t will still yield "Explorer" as if the desktop still had focus. However, pressing tab clearly shows that Firefox had focus because it performs the expected action of jumping, for example, out of the address field and into the search field.
For an experiment I gave it a full five minutes to see if it just takes an awful lot of time, but no luck. So, window activation events seem under certain conditions to be able to pass under NVDA's radar.
It might be worth noting that I noticed this not long after a reboot and the dust might not have fully settled in terms of background tasks starting and stopping.
Kind regards,
Felix

Re: getting NVDA to indicate capital letters

Gene
 

I may have written NVDA v but I meant NVDA control v.  The voice settings dialog is also accessible from the NVDA menus. 
Sorry for the mistake.

Gene
----- Original Message -----
From: Dennis L
Sent: Friday, February 24, 2017 8:38 PM
Subject: Re: [nvda] getting NVDA to indicate capital letters

When I press nvda v nothing happens.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..

Re: getting NVDA to indicate capital letters

Gene
 

Yes.  Why not experiment in such a case.  You can't do any harm. 
 
Gene

From: Dennis L
Sent: Friday, February 24, 2017 8:38 PM
Subject: Re: [nvda] getting NVDA to indicate capital letters

What gets it to be a higher pitch the higher the number?

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..

Re: getting NVDA to indicate capital letters

Dennis L <dennisl1982@...>
 

I have appeared to track it down.  The problem is two pronged.  1 you can’t have eloquence for windows and the NVDA eloquence/vocalizer add-on installed at the same time.  2 You can’t have force pitch checked.  It overrides NVDA’s behavior.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Mendoza
Sent: Saturday, February 25, 2017 1:14 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Alright then, maybe someone could shell out some advice from our fellow listers if they are using the same case you have. That's all I could give an advise for now.


Robert Mendoza

On 2/25/2017 1:59 PM, Dennis L wrote:

It is the eloquence adon from codefactory.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Mendoza
Sent: Saturday, February 25, 2017 12:54 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

That's kindly odd to know. I may asked what version of nvda that was installed to your machine? or perhaps tried to disable all the addons by restarting to double check the problem. I don't think any possible could have trigger a problem other than that because it works fine from here at all. Or, the last option will be resetting the nvda to factory default to ensure you made all the possible troubleshooting.



Robert Mendoza

On 2/25/2017 1:38 PM, Dennis L wrote:

I increased it but didn’t notice any difference

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Mendoza
Sent: Saturday, February 25, 2017 12:22 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

It seems you just increases the pitch volume of the voice itself. But, you were able to tabbed through till you heard that says "Capital pitch change percentage 30", The numeric or the edit field of 30 was the default You can increases it that the value on your preferred or desired value you like. Then, pressed Okay to take apply the changes.




Robert Mendoza

On 2/25/2017 11:37 AM, Dennis L wrote:

I tried that nothing happened. When I got to the setting I didn't notice a difference after making the number higher.

Sent from my Android phone using Aqua Mail

On February 24, 2017 10:31:05 PM "Robert Mendoza" <lowvisiontek@...> wrote:

You may pressed nvda plus control V, to go directly of the Voice Setting options. Then, follow the steps mentioned below as per suggested earlier to this thread.




Robert Mendoza

On 2/25/2017 10:38 AM, Dennis L wrote:

When I press nvda v nothing happens.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..

 

 

 

 

Re: getting NVDA to indicate capital letters

Robert Mendoza
 

Alright then, maybe someone could shell out some advice from our fellow listers if they are using the same case you have. That's all I could give an advise for now.

Robert Mendoza
On 2/25/2017 1:59 PM, Dennis L wrote:

It is the eloquence adon from codefactory.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Mendoza
Sent: Saturday, February 25, 2017 12:54 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

That's kindly odd to know. I may asked what version of nvda that was installed to your machine? or perhaps tried to disable all the addons by restarting to double check the problem. I don't think any possible could have trigger a problem other than that because it works fine from here at all. Or, the last option will be resetting the nvda to factory default to ensure you made all the possible troubleshooting.


Robert Mendoza

On 2/25/2017 1:38 PM, Dennis L wrote:

I increased it but didn’t notice any difference

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Mendoza
Sent: Saturday, February 25, 2017 12:22 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

It seems you just increases the pitch volume of the voice itself. But, you were able to tabbed through till you heard that says "Capital pitch change percentage 30", The numeric or the edit field of 30 was the default You can increases it that the value on your preferred or desired value you like. Then, pressed Okay to take apply the changes.



Robert Mendoza

On 2/25/2017 11:37 AM, Dennis L wrote:

I tried that nothing happened. When I got to the setting I didn't notice a difference after making the number higher.

Sent from my Android phone using Aqua Mail

On February 24, 2017 10:31:05 PM "Robert Mendoza" <lowvisiontek@...> wrote:

You may pressed nvda plus control V, to go directly of the Voice Setting options. Then, follow the steps mentioned below as per suggested earlier to this thread.



Robert Mendoza

On 2/25/2017 10:38 AM, Dennis L wrote:

When I press nvda v nothing happens.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..

 

 

 


Headers in Microsoft Word

Simon Jaeger
 

hi,

Any idea how I can read these? Seems like a stupid thing to install a 40 minute JAWS demo for.


Simon

Re: getting NVDA to indicate capital letters

Dennis L <dennisl1982@...>
 

It is the eloquence adon from codefactory.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Mendoza
Sent: Saturday, February 25, 2017 12:54 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

That's kindly odd to know. I may asked what version of nvda that was installed to your machine? or perhaps tried to disable all the addons by restarting to double check the problem. I don't think any possible could have trigger a problem other than that because it works fine from here at all. Or, the last option will be resetting the nvda to factory default to ensure you made all the possible troubleshooting.


Robert Mendoza

On 2/25/2017 1:38 PM, Dennis L wrote:

I increased it but didn’t notice any difference

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Mendoza
Sent: Saturday, February 25, 2017 12:22 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

It seems you just increases the pitch volume of the voice itself. But, you were able to tabbed through till you heard that says "Capital pitch change percentage 30", The numeric or the edit field of 30 was the default You can increases it that the value on your preferred or desired value you like. Then, pressed Okay to take apply the changes.



Robert Mendoza

On 2/25/2017 11:37 AM, Dennis L wrote:

I tried that nothing happened. When I got to the setting I didn't notice a difference after making the number higher.

Sent from my Android phone using Aqua Mail

On February 24, 2017 10:31:05 PM "Robert Mendoza" <lowvisiontek@...> wrote:

You may pressed nvda plus control V, to go directly of the Voice Setting options. Then, follow the steps mentioned below as per suggested earlier to this thread.



Robert Mendoza

On 2/25/2017 10:38 AM, Dennis L wrote:

When I press nvda v nothing happens.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..

 

 

 

Re: getting NVDA to indicate capital letters

Robert Mendoza
 

That's kindly odd to know. I may asked what version of nvda that was installed to your machine? or perhaps tried to disable all the addons by restarting to double check the problem. I don't think any possible could have trigger a problem other than that because it works fine from here at all. Or, the last option will be resetting the nvda to factory default to ensure you made all the possible troubleshooting.

Robert Mendoza
On 2/25/2017 1:38 PM, Dennis L wrote:

I increased it but didn’t notice any difference

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Mendoza
Sent: Saturday, February 25, 2017 12:22 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

It seems you just increases the pitch volume of the voice itself. But, you were able to tabbed through till you heard that says "Capital pitch change percentage 30", The numeric or the edit field of 30 was the default You can increases it that the value on your preferred or desired value you like. Then, pressed Okay to take apply the changes.


Robert Mendoza

On 2/25/2017 11:37 AM, Dennis L wrote:

I tried that nothing happened. When I got to the setting I didn't notice a difference after making the number higher.

Sent from my Android phone using Aqua Mail

On February 24, 2017 10:31:05 PM "Robert Mendoza" <lowvisiontek@...> wrote:

You may pressed nvda plus control V, to go directly of the Voice Setting options. Then, follow the steps mentioned below as per suggested earlier to this thread.


Robert Mendoza

On 2/25/2017 10:38 AM, Dennis L wrote:

When I press nvda v nothing happens.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..

 

 


Re: Questions and suggestions

Kwork
 


As I said, this has already been hashed to death, and it's obvious that the NVDA developers will continue to ignore the request of some of us users, including a current moderator on this list, so I see no need to respond to your specific inquiries as Gene already addressed them in an earlier message, especially the fallibility of the erroneous belief that the Windows command always accesses everything it should. The add-on usually does a better job than the Win+b command, and whatever Jaws uses does the best job of all.
Travis

----- Original Message -----
Sent: Friday, February 24, 2017 8:35 PM
Subject: Re: [nvda] Questions and suggestions

This argument is silly.

The windows-b key gives you access, what's the issue?  Windows-b works regardless of screen reader, windows version, or desktop/laptop keyboard layout.  I see no problem here, and arguing that other screen readers provide another keystroke for the same function is a spurious argument.  Other windows screen readers aren't open source either, but I don't see anyone pushing to have this fixed.  Other windows screen readers also tend to be larger, and take up more system resources (on average) but I don't see anyone complaining about this either.  Just because other screen readers have something doesn't automatically make it something NVDA *must* have.  Windows provides the keystroke windows-b for a reason, and there's no reason to duplicate the effort by building access to the same function just because you can.

Good lord, if folks wanted every single windows function duplicated, just imagine how much bloat screen readers would have.  Nothing wrong with leaving windows keystrokes alone, and just pointing them out when someone asks.  No need to needlessly duplicate existing functionality.  Should NVDA provide another keystroke to switch between programs when alt-tab does the job just fine?

Give it a rest already.



On 2/24/2017 5:34 PM, Kwork wrote:
Agreed here completely. This should be a core NVDA function, and not only available by installing an add-on. But this has been hashed out before, with NVDA developers ignoring the desires of some of us users.
Travis
----- Original Message -----
From: Gene
Sent: Thursday, February 23, 2017 10:29 PM
Subject: Re: [nvda] Questions and suggestions

That isn't the reason and that argument is irrelevant.  The system tray wasn't accessible years ago through Windows.  There needed to be a screen-reader dialog to provide access.  That's how the whole separate access got started and System Access uses the same command.  Window-eyes uses a different command but it too provides a system tray dialog. 
 
There are times, like it or not, when the dialog works better than using the Windows access method and it should be provided as a part of screen-readers. 
 
Sometimes, I get access to something using the Windows method when the dialog doesn't work properly and at other times, I have found the only way I've gotten access to an item is by using the dialog.  These instances where one or the other method doesn't work are rare but the argument that the screen-reader dialog method is nothing but duplication is not correct. 
Gene
----- Original Message -----
Sent: Thursday, February 23, 2017 10:21 PM
Subject: Re: [nvda] Questions and suggestions

Because NVDA is not jaws, and there's no reason to make it mirror jaws keystrokes.  The windows-b keystroke will work no matter what you use for a screen reader, since it's a windows command.  That's why NVDA uses it.  There is no dedicated NVDA keystroke for this function.



On 2/23/2017 8:36 PM, Arlene wrote:

Hi, I don’t know if I can say here! When you go to your system trey. Why not make future builds of NVDA be insert F 11? Instead of windows B. 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Damien Sykes-Lindley
Sent: February-23-17 9:06 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Questions and suggestions

 

Hi Gene,

Hotkeys are indeed excellent. One of the first thing I look for in a program is hotkeys. In fact, some have so many that it’s hard to memorise all of them. But at least they’re there!

The only problem I have with Windows shortcuts being linked to them is that, because they are global throughout the whole system, it can unfortunately cause conflicts with other running applications that utilise those shortcuts. For instance, I could assign a ctrl+alt+q shortcut to launch QWS (a MIDI sequencer), and another application may use ctrl+alt+q to mean quit. I have known ctrl+alt+o for options, ctrl+alt+x for exit, ctrl+alt+n/p for next/previous, all of which can be assigned to a Windows hotkey, and then it’s touch and go as to which item activates. Otherwise, I’m definitely all for hotkeys!

As an aside, I must admit I do find it odd, and mildly frustrating that there are four modifier keys that can be used to register hotkeys and yet it is still possible to run out of logical keys! This is even more so for global shortcut-linked ones, since I think you can only have ctrl+alt and ctrl+shift combos. Possibly if you’re extremely dextrous you might be able to have ctrl+shift+alt, I haven’t dared to try that one. Lol.

First letter navigation. Now you mention it I am aware of it. I use it all the time to move quickly to files in Explorer. But for some reason it didn’t cross my mind for the desktop (even though I know that is also controlled by explorer). I guess because my explorer is in detail view, and the desktop shows as a sort of grid layout I treated them as two separate systems. Strange how brains work!

Cheers.
Damien.





Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com






Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


Re: getting NVDA to indicate capital letters

Dennis L <dennisl1982@...>
 

I increased it but didn’t notice any difference

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Robert Mendoza
Sent: Saturday, February 25, 2017 12:22 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

It seems you just increases the pitch volume of the voice itself. But, you were able to tabbed through till you heard that says "Capital pitch change percentage 30", The numeric or the edit field of 30 was the default You can increases it that the value on your preferred or desired value you like. Then, pressed Okay to take apply the changes.


Robert Mendoza

On 2/25/2017 11:37 AM, Dennis L wrote:

I tried that nothing happened. When I got to the setting I didn't notice a difference after making the number higher.

Sent from my Android phone using Aqua Mail

On February 24, 2017 10:31:05 PM "Robert Mendoza" <lowvisiontek@...> wrote:

You may pressed nvda plus control V, to go directly of the Voice Setting options. Then, follow the steps mentioned below as per suggested earlier to this thread.


Robert Mendoza

On 2/25/2017 10:38 AM, Dennis L wrote:

When I press nvda v nothing happens.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..

 

 

Re: getting NVDA to indicate capital letters

Robert Mendoza
 

It seems you just increases the pitch volume of the voice itself. But, you were able to tabbed through till you heard that says "Capital pitch change percentage 30", The numeric or the edit field of 30 was the default You can increases it that the value on your preferred or desired value you like. Then, pressed Okay to take apply the changes.

Robert Mendoza
On 2/25/2017 11:37 AM, Dennis L wrote:

I tried that nothing happened. When I got to the setting I didn't notice a difference after making the number higher.

Sent from my Android phone using Aqua Mail

On February 24, 2017 10:31:05 PM "Robert Mendoza" <lowvisiontek@...> wrote:

You may pressed nvda plus control V, to go directly of the Voice Setting options. Then, follow the steps mentioned below as per suggested earlier to this thread.

Robert Mendoza
On 2/25/2017 10:38 AM, Dennis L wrote:

When I press nvda v nothing happens.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..



Re: getting NVDA to indicate capital letters

Dennis L <dennisl1982@...>
 

I tried that nothing happened. When I got to the setting I didn't notice a difference after making the number higher.

Sent from my Android phone using Aqua Mail

On February 24, 2017 10:31:05 PM "Robert Mendoza" <lowvisiontek@...> wrote:

You may pressed nvda plus control V, to go directly of the Voice Setting options. Then, follow the steps mentioned below as per suggested earlier to this thread.

Robert Mendoza
On 2/25/2017 10:38 AM, Dennis L wrote:

When I press nvda v nothing happens.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..


Re: Questions and suggestions

Travis Siegel <tsiegel@...>
 

This argument is silly.

The windows-b key gives you access, what's the issue?  Windows-b works regardless of screen reader, windows version, or desktop/laptop keyboard layout.  I see no problem here, and arguing that other screen readers provide another keystroke for the same function is a spurious argument.  Other windows screen readers aren't open source either, but I don't see anyone pushing to have this fixed.  Other windows screen readers also tend to be larger, and take up more system resources (on average) but I don't see anyone complaining about this either.  Just because other screen readers have something doesn't automatically make it something NVDA *must* have.  Windows provides the keystroke windows-b for a reason, and there's no reason to duplicate the effort by building access to the same function just because you can.

Good lord, if folks wanted every single windows function duplicated, just imagine how much bloat screen readers would have.  Nothing wrong with leaving windows keystrokes alone, and just pointing them out when someone asks.  No need to needlessly duplicate existing functionality.  Should NVDA provide another keystroke to switch between programs when alt-tab does the job just fine?

Give it a rest already.



On 2/24/2017 5:34 PM, Kwork wrote:
Agreed here completely. This should be a core NVDA function, and not only available by installing an add-on. But this has been hashed out before, with NVDA developers ignoring the desires of some of us users.
Travis
----- Original Message -----
From: Gene
Sent: Thursday, February 23, 2017 10:29 PM
Subject: Re: [nvda] Questions and suggestions

That isn't the reason and that argument is irrelevant.  The system tray wasn't accessible years ago through Windows.  There needed to be a screen-reader dialog to provide access.  That's how the whole separate access got started and System Access uses the same command.  Window-eyes uses a different command but it too provides a system tray dialog. 
 
There are times, like it or not, when the dialog works better than using the Windows access method and it should be provided as a part of screen-readers. 
 
Sometimes, I get access to something using the Windows method when the dialog doesn't work properly and at other times, I have found the only way I've gotten access to an item is by using the dialog.  These instances where one or the other method doesn't work are rare but the argument that the screen-reader dialog method is nothing but duplication is not correct. 
Gene
----- Original Message -----
Sent: Thursday, February 23, 2017 10:21 PM
Subject: Re: [nvda] Questions and suggestions

Because NVDA is not jaws, and there's no reason to make it mirror jaws keystrokes.  The windows-b keystroke will work no matter what you use for a screen reader, since it's a windows command.  That's why NVDA uses it.  There is no dedicated NVDA keystroke for this function.



On 2/23/2017 8:36 PM, Arlene wrote:

Hi, I don’t know if I can say here! When you go to your system trey. Why not make future builds of NVDA be insert F 11? Instead of windows B. 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Damien Sykes-Lindley
Sent: February-23-17 9:06 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Questions and suggestions

 

Hi Gene,

Hotkeys are indeed excellent. One of the first thing I look for in a program is hotkeys. In fact, some have so many that it’s hard to memorise all of them. But at least they’re there!

The only problem I have with Windows shortcuts being linked to them is that, because they are global throughout the whole system, it can unfortunately cause conflicts with other running applications that utilise those shortcuts. For instance, I could assign a ctrl+alt+q shortcut to launch QWS (a MIDI sequencer), and another application may use ctrl+alt+q to mean quit. I have known ctrl+alt+o for options, ctrl+alt+x for exit, ctrl+alt+n/p for next/previous, all of which can be assigned to a Windows hotkey, and then it’s touch and go as to which item activates. Otherwise, I’m definitely all for hotkeys!

As an aside, I must admit I do find it odd, and mildly frustrating that there are four modifier keys that can be used to register hotkeys and yet it is still possible to run out of logical keys! This is even more so for global shortcut-linked ones, since I think you can only have ctrl+alt and ctrl+shift combos. Possibly if you’re extremely dextrous you might be able to have ctrl+shift+alt, I haven’t dared to try that one. Lol.

First letter navigation. Now you mention it I am aware of it. I use it all the time to move quickly to files in Explorer. But for some reason it didn’t cross my mind for the desktop (even though I know that is also controlled by explorer). I guess because my explorer is in detail view, and the desktop shows as a sort of grid layout I treated them as two separate systems. Strange how brains work!

Cheers.
Damien.





Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com






Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


Re: getting NVDA to indicate capital letters

Robert Mendoza
 

You may pressed nvda plus control V, to go directly of the Voice Setting options. Then, follow the steps mentioned below as per suggested earlier to this thread.

Robert Mendoza
On 2/25/2017 10:38 AM, Dennis L wrote:

When I press nvda v nothing happens.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, February 24, 2017 9:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] getting NVDA to indicate capital letters

 

Open voice settings with NVDA key v. 

Tab through the items in the dialog and you'll see an edit field where you can type a numeric entry for the pitch of capital letters.

 

Gene

----- Original Message -----

From: Dennis L

Sent: Friday, February 24, 2017 6:36 PM

Subject: [nvda] getting NVDA to indicate capital letters

 

Hi,  is there any way to get NVDA  to indicate capital letters with a higher pitch sound in the TTs similar to Jaws?  Thanks..