Windows OneCore Voices Not Reading dialog in f2 rename field and control-shift-n New Folder field


Nancy Shackelford
 

How do I make the Onecore voices read these fields?
Thanks,
Nance

--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--


 

This is also the case with eSpeak NG voices, but I have no idea if this is a new behavior or not.

I do know that if, after you've finished typing the name (or rename) and hitting enter, if you down arrow or up arrow off of the folder that was created with a new name or renamed, it will be announced, but it seems to me that you should be able to force NVDA to read what has been typed in the folder name itself, and I can't do that for either situation when actually creating the name or renaming.
--

Brian Virginia, USA Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881


Gene
 

I would suggest running NVDA with no add-ons to be sure this isn't caused by a combination of the new NVDA and an add-on.  Using Windows 10 and NVDA with no add-ons, I have no such problem.

I'm using Windows version 22H2 and NVDA version 2023.1.

Gene

On 3/27/2023 9:13 AM, Nancy Shackelford wrote:

How do I make the Onecore voices read these fields?
Thanks,
Nance

--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--


 

Just to be 100% clear, even though it's embedded in my signature, my testing is being done on Windows 11, Version 22H2, with NVDA 2023.1, but with the add-ons I've been using still active.  I'll check later with add-ons disabled.
--

Brian Virginia, USA Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881


Nancy Shackelford
 

Only 2 addons I had are both incompatible at present, so I just removed them. Reading situation still the same.
Nance


On Mon, Mar 27, 2023 at 9:46 AM Gene <gsasner@...> wrote:
I would suggest running NVDA with no add-ons to be sure this isn't caused by a combination of the new NVDA and an add-on.  Using Windows 10 and NVDA with no add-ons, I have no such problem.

I'm using Windows version 22H2 and NVDA version 2023.1.

Gene

On 3/27/2023 9:13 AM, Nancy Shackelford wrote:
How do I make the Onecore voices read these fields?
Thanks,
Nance

--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--



--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--


 

Nance,

We know you're talking about NVDA 2023.1, unadorned, but what is the Windows ecosystem under which you're using it?  If it's Windows 10, then we have a difference between two machines with the same setup.  If it's Windows 11, then so far we have two reports of the same behavior.  This could be "a Windows thing."

This is why, right now, I am begging people to include Windows Edition, Version, and main Build number, as well as NVDA version number and the version number of the software NVDA's being used to access (when relevant, and it's not here, since you're accessing a built-in Windows feature).
--

Brian Virginia, USA Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881


Gene
 

You didn't have to remove them.  If they are incompatible, they are automatically disabled during installation of the new version. 

Also, as I understand it, if you leave the incompatible add-ons, add-on updater will find add-ons for them if compatible add-ons become available and if you have it look in sources where the add-ons are.  If you remove them, it won't look because they won't be there.  So people should leave incompatible add-ons in place if they want to use add-on updater to look for them in future.

Gene

On 3/27/2023 10:12 AM, Nancy Shackelford wrote:

Only 2 addons I had are both incompatible at present, so I just removed them. Reading situation still the same.
Nance

On Mon, Mar 27, 2023 at 9:46 AM Gene <gsasner@...> wrote:
I would suggest running NVDA with no add-ons to be sure this isn't caused by a combination of the new NVDA and an add-on.  Using Windows 10 and NVDA with no add-ons, I have no such problem.

I'm using Windows version 22H2 and NVDA version 2023.1.

Gene

On 3/27/2023 9:13 AM, Nancy Shackelford wrote:
How do I make the Onecore voices read these fields?
Thanks,
Nance

--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--



--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--


Nancy Shackelford
 

I looked at the Codefactory but not the emoticons. I just restarted N V D A after removing the incompatible addons, and the fields discussed above are now being read, at least the new folder field is read character by character, but the f2 rename field is not read except for reading the current line; at least this is some improvement.
Thanks,
Nance.

On Mon, Mar 27, 2023 at 10:35 AM Gene <gsasner@...> wrote:
You didn't have to remove them.  If they are incompatible, they are automatically disabled during installation of the new version. 

Also, as I understand it, if you leave the incompatible add-ons, add-on updater will find add-ons for them if compatible add-ons become available and if you have it look in sources where the add-ons are.  If you remove them, it won't look because they won't be there.  So people should leave incompatible add-ons in place if they want to use add-on updater to look for them in future.

Gene

On 3/27/2023 10:12 AM, Nancy Shackelford wrote:
Only 2 addons I had are both incompatible at present, so I just removed them. Reading situation still the same.
Nance

On Mon, Mar 27, 2023 at 9:46 AM Gene <gsasner@...> wrote:
I would suggest running NVDA with no add-ons to be sure this isn't caused by a combination of the new NVDA and an add-on.  Using Windows 10 and NVDA with no add-ons, I have no such problem.

I'm using Windows version 22H2 and NVDA version 2023.1.

Gene

On 3/27/2023 9:13 AM, Nancy Shackelford wrote:
How do I make the Onecore voices read these fields?
Thanks,
Nance

--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--



--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--



--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--


Luke Davis
 

Nancy Shackelford wrote:

Only 2 addons I had are both incompatible at present, so I just removed them.
Why remove them? Why not just wait for them to update when compatible versions are available?

Incompatible add-ons are simply disabled, they don't hurt anything.

Luke


Brian's Mail list account
 

Well for Espeak this worked as you would expect on Windows 7, so maybe some odd update has broken it in windows itself?
. The 10 machine is elsewhere today, so cannot test this.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Brian Vogel" <britechguy@...>
To: <nvda@nvda.groups.io>
Sent: Monday, March 27, 2023 3:38 PM
Subject: Re: [nvda] Windows OneCore Voices Not Reading dialog in f2 rename field and control-shift-n New Folder field


This is also the case with eSpeak NG voices, but I have no idea if this is a new behavior or not.

I do know that if, after you've finished typing the name (or rename) and hitting enter, if you down arrow or up arrow off of the folder that was created with a new name or renamed, it will be announced, but it seems to me that you should be able to force NVDA to read what has been typed in the folder name itself, and I can't do that for either situation when actually creating the name or renaming.
--

Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

*It is much easier to be critical than to be correct.*

~ Benjamin Disraeli, 1804-1881


Brian's Mail list account
 

What happens if you can find it, can use the ribbon option for rename instead. I say if you can find it as its still doing my brain in.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Nancy Shackelford" <n.k.nancelady@...>
To: <nvda@nvda.groups.io>
Sent: Monday, March 27, 2023 5:06 PM
Subject: Re: [nvda] Windows OneCore Voices Not Reading dialog in f2 rename field and control-shift-n New Folder field


I looked at the Codefactory but not the emoticons. I just restarted N V D A
after removing the incompatible addons, and the fields discussed above are
now being read, at least the new folder field is read character by
character, but the f2 rename field is not read except for reading the
current line; at least this is some improvement.
Thanks,
Nance.

On Mon, Mar 27, 2023 at 10:35 AM Gene <gsasner@...> wrote:

You didn't have to remove them. If they are incompatible, they are
automatically disabled during installation of the new version.

Also, as I understand it, if you leave the incompatible add-ons, add-on
updater will find add-ons for them if compatible add-ons become available
and if you have it look in sources where the add-ons are. If you remove
them, it won't look because they won't be there. So people should leave
incompatible add-ons in place if they want to use add-on updater to look
for them in future.

Gene

On 3/27/2023 10:12 AM, Nancy Shackelford wrote:

Only 2 addons I had are both incompatible at present, so I just removed
them. Reading situation still the same.
Nance

On Mon, Mar 27, 2023 at 9:46 AM Gene <gsasner@...> wrote:

I would suggest running NVDA with no add-ons to be sure this isn't caused
by a combination of the new NVDA and an add-on. Using Windows 10 and NVDA
with no add-ons, I have no such problem.

I'm using Windows version 22H2 and NVDA version 2023.1.

Gene

On 3/27/2023 9:13 AM, Nancy Shackelford wrote:

How do I make the Onecore voices read these fields?
Thanks,
Nance

--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--


--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--




--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--


Gene
 

You don't have to use the ribbon.  You can use the context menu.  When you are on a file, open the context menu, find rename, and press enter. 

Ribbon programs have other ways to do many things that have nothing to do with the ribbons.  That makes the ribbons less problem for those who dislike them.  and for certain things, you have to use other nonribbon methods for.  For example, opening options is usually not done in the ribbons.

There is the context menu.  There is also the one other menu all ribbon programs have.  You can bring it up with alt f.  Hold alt and type f.  Usually, options is in that menu.  If you use save as, usually alt f followed by a, you are using the menu. 
And a lot or perhaps all of the old control plus letter commands still work such as control, open, etc.

Gene
On 3/28/2023 3:04 AM, Brian's Mail list account via groups.io wrote:

On 3/28/2023 3:04 AM, Brian's Mail list account via groups.io wrote:

What happens if you  can find it, can use the  ribbon option for rename instead. I say if you can find it as its still doing my brain in.
Brian



Nancy Shackelford
 

One should just be able to hit the Applications key for the context menu. It wasn't getting to the rename field that was the problem--it was that N V D A wasn't reading anything one tried to type into the field. I just opened Notepad and typed in what I wanted in the Rename field, copied it, and pasted it into that field. Worked fine!
Nance

Virus-free.www.avast.com


On Tue, Mar 28, 2023 at 7:42 AM Gene <gsasner@...> wrote:
You don't have to use the ribbon.  You can use the context menu.  When you are on a file, open the context menu, find rename, and press enter. 

Ribbon programs have other ways to do many things that have nothing to do with the ribbons.  That makes the ribbons less problem for those who dislike them.  and for certain things, you have to use other nonribbon methods for.  For example, opening options is usually not done in the ribbons.

There is the context menu.  There is also the one other menu all ribbon programs have.  You can bring it up with alt f.  Hold alt and type f.  Usually, options is in that menu.  If you use save as, usually alt f followed by a, you are using the menu. 
And a lot or perhaps all of the old control plus letter commands still work such as control, open, etc.

Gene
On 3/28/2023 3:04 AM, Brian's Mail list account via groups.io wrote:

On 3/28/2023 3:04 AM, Brian's Mail list account via groups.io wrote:
What happens if you  can find it, can use the  ribbon option for rename instead. I say if you can find it as its still doing my brain in.
Brian




--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--


Gene
 

In future, you should be able to just press f2, type what you want and press enter.  You aren't able to read what is in the field but that doesn't mean you aren't in it.  If you could paste material into the field, you can also type in the field.

Also, if you haven't tried Narrator or JAWS, you might want to try that.  If you can read the field with other screen-readers, it is a problem related to NVDA or one or more add-ons.  If you can't read the field, the problem isn't an NVDA problem.

In Narrator, the command for read current line is numpad insert numpad 8, just as it is in JAWS.

Gene

On 3/28/2023 8:10 AM, Nancy Shackelford wrote:

One should just be able to hit the Applications key for the context menu. It wasn't getting to the rename field that was the problem--it was that N V D A wasn't reading anything one tried to type into the field. I just opened Notepad and typed in what I wanted in the Rename field, copied it, and pasted it into that field. Worked fine!
Nance

Virus-free.www.avast.com

On Tue, Mar 28, 2023 at 7:42 AM Gene <gsasner@...> wrote:
You don't have to use the ribbon.  You can use the context menu.  When you are on a file, open the context menu, find rename, and press enter. 

Ribbon programs have other ways to do many things that have nothing to do with the ribbons.  That makes the ribbons less problem for those who dislike them.  and for certain things, you have to use other nonribbon methods for.  For example, opening options is usually not done in the ribbons.

There is the context menu.  There is also the one other menu all ribbon programs have.  You can bring it up with alt f.  Hold alt and type f.  Usually, options is in that menu.  If you use save as, usually alt f followed by a, you are using the menu. 
And a lot or perhaps all of the old control plus letter commands still work such as control, open, etc.

Gene
On 3/28/2023 3:04 AM, Brian's Mail list account via groups.io wrote:

On 3/28/2023 3:04 AM, Brian's Mail list account via groups.io wrote:
What happens if you  can find it, can use the  ribbon option for rename instead. I say if you can find it as its still doing my brain in.
Brian




--
Nancy Shackelford --Walk On Faith And Trust In Love - Michael Reid--


Sarah k Alawami
 

I was just able to reproduce this with eloquence, and now running nvda 2023.something, sorry. I need to actually look and update my now outdated signature.  Anyway nothing happens when I arrow, and in this case, all I  need to change is 1 character. I cannot get to it now, which really sucks. I tested with my portable copy and hitting f2 does not result in the text being read out like it used to.  Not even hitting control shift to select reads the text. This looks like a windows issue to me.  I think I’ve had this issue now for a few weeks but thought it was just me. Apparently not.

 

Windows 11 22H2 (AMD64) build 22621.1413

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Tuesday, March 28, 2023 6:24 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows OneCore Voices Not Reading dialog in f2 rename field and control-shift-n New Folder field

 

In future, you should be able to just press f2, type what you want and press enter.  You aren't able to read what is in the field but that doesn't mean you aren't in it.  If you could paste material into the field, you can also type in the field.

Also, if you haven't tried Narrator or JAWS, you might want to try that.  If you can read the field with other screen-readers, it is a problem related to NVDA or one or more add-ons.  If you can't read the field, the problem isn't an NVDA problem.

In Narrator, the command for read current line is numpad insert numpad 8, just as it is in JAWS.

Gene

On 3/28/2023 8:10 AM, Nancy Shackelford wrote:

One should just be able to hit the Applications key for the context menu. It wasn't getting to the rename field that was the problem--it was that N V D A wasn't reading anything one tried to type into the field. I just opened Notepad and typed in what I wanted in the Rename field, copied it, and pasted it into that field. Worked fine!

Nance

 

You don't have to use the ribbon.  You can use the context menu.  When you are on a file, open the context menu, find rename, and press enter. 

Ribbon programs have other ways to do many things that have nothing to do with the ribbons.  That makes the ribbons less problem for those who dislike them.  and for certain things, you have to use other nonribbon methods for.  For example, opening options is usually not done in the ribbons.

There is the context menu.  There is also the one other menu all ribbon programs have.  You can bring it up with alt f.  Hold alt and type f.  Usually, options is in that menu.  If you use save as, usually alt f followed by a, you are using the menu. 
And a lot or perhaps all of the old control plus letter commands still work such as control, open, etc.

Gene
On 3/28/2023 3:04 AM, Brian's Mail list account via groups.io wrote:

What happens if you  can find it, can use the  ribbon option for rename instead. I say if you can find it as its still doing my brain in.
Brian

 



--

 


--
----------

Sarah Alawami, owner of flying Blind.  Visit my website to read my story. 

Windows 11 22H2 (x64) build 22621.963
NVDA Version: 2022.3.3

Microsoft 365 MSO (Version 2211 Build 16.0.15831.20098) 64-bit 


 

On Tue, Mar 28, 2023 at 09:23 AM, Gene wrote:
You aren't able to read what is in the field but that doesn't mean you aren't in it.
-
This is one of those things I can't seem to get many people to understand, regardless of visual status.  The moment you hit F2 to rename, you are put in edit mode and the entirety of the existing name (or file name, without extension, depending on how you have your system set up) is already selected and you can just begin typing its replacement.  If it's an insanely long name, since it's selected, you can just hit CTRL + C to copy it, paste it in to something like clipboard, edit it there, then copy what you have there and paste it back in the rename edit box.

I agree that something's wrong here, but that's not my point.  Regardless of visual status, people really need to learn how things work when everything is working as expected (which is most of the time for something like rename, cut, copy, paste) and trust that if you're issuing certain commands that the things they do are happening.  If you've selected something (be it a file, text in a document, etc.) and know what that is, if you hit CTRL + X to cut it, it's cut, or CTRL + C to copy it, it's copied.  None of this is presented visually (at least for copy - cut makes text disappear or files to be presented as "veiled" for lack of a better description) to me or any sighted user, we just know it's happened.

If great care is needed in renaming a long file name, for the time being after the file/folder is selected:
1. Hit F2.
2. Hit CTRL + C
3. Open notepad then hit CTRL + V
4. Edit what's in notepad to what you want.
5. Hit CTRL + A to select all, then CTRL + C (or CTRL + X) to copy (or cut) it.
6. Go back to file explorer, make certain the file/folder you need to rename is selected, hit F2 again.
7. Hit CTRL + V to paste the thing you copied or cut as the new name, then hit Enter.

Mind you, that's only for things that have insanely complex names.  If I were renaming something called brian.txt to something called vogel.txt I'd just hit F2, type vogel.txt, hit enter and be done with it.
--

Brian Virginia, USA Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881


Sarah k Alawami
 

Yep, I just did that for my folders. I hope this gets fixed. I’m not sure if this is annvda issue or a windows itself issue as I have not yet tested withnarrator.

Update, I just tested w narrator and the issue happens there as well. So looks like this is a windows issue not nvda related. Well a coppyin I go, a coppyin I go. Hi ho the darrio, a coppyin I go.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Wednesday, March 29, 2023 8:48 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows OneCore Voices Not Reading dialog in f2 rename field and control-shift-n New Folder field

 

On Tue, Mar 28, 2023 at 09:23 AM, Gene wrote:

You aren't able to read what is in the field but that doesn't mean you aren't in it.

-
This is one of those things I can't seem to get many people to understand, regardless of visual status.  The moment you hit F2 to rename, you are put in edit mode and the entirety of the existing name (or file name, without extension, depending on how you have your system set up) is already selected and you can just begin typing its replacement.  If it's an insanely long name, since it's selected, you can just hit CTRL + C to copy it, paste it in to something like clipboard, edit it there, then copy what you have there and paste it back in the rename edit box.

I agree that something's wrong here, but that's not my point.  Regardless of visual status, people really need to learn how things work when everything is working as expected (which is most of the time for something like rename, cut, copy, paste) and trust that if you're issuing certain commands that the things they do are happening.  If you've selected something (be it a file, text in a document, etc.) and know what that is, if you hit CTRL + X to cut it, it's cut, or CTRL + C to copy it, it's copied.  None of this is presented visually (at least for copy - cut makes text disappear or files to be presented as "veiled" for lack of a better description) to me or any sighted user, we just know it's happened.

If great care is needed in renaming a long file name, for the time being after the file/folder is selected:
1. Hit F2.
2. Hit CTRL + C
3. Open notepad then hit CTRL + V
4. Edit what's in notepad to what you want.
5. Hit CTRL + A to select all, then CTRL + C (or CTRL + X) to copy (or cut) it.
6. Go back to file explorer, make certain the file/folder you need to rename is selected, hit F2 again.
7. Hit CTRL + V to paste the thing you copied or cut as the new name, then hit Enter.

Mind you, that's only for things that have insanely complex names.  If I were renaming something called brian.txt to something called vogel.txt I'd just hit F2, type vogel.txt, hit enter and be done with it.
--

Brian Virginia, USA Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881


--
----------

Sarah Alawami, owner of flying Blind.  Visit my website to read my story. 

Windows 11 22H2 (x64) build 22621.963
NVDA Version: 2022.3.3

Microsoft 365 MSO (Version 2211 Build 16.0.15831.20098) 64-bit