Can anyone tell me where I can find it in NVDA please?

Had a look through the settings and no luck.

 

Can anyone tell me where I can find it in NVDA please?

Had a look through the settings and no luck.

 

At the risk of being off topic, but hopefully not, why would you use them?

I ask because I looked into them. The thing I'd want to do is have them be saved and put stuff on them, e.g. all my audio stuff on one, games on another, something like that. But the big thing it seems to do is have apps/windows open on them. So for example, as I understand it, instead of running Firefox and Thunderbird and Skype and a game, and switching between four windows with alt-tab, I could put Firefox and Thunderbird on their own desktop.

But then that means I have to hit ctrl-win-left/right arrow to get to whatever desktop they're on, and then once I'm there, alt-tab between windows. Additionally, as I understand it, while it saves the desktops if you restart, you have to open whatever you want on each desktop again, it doesn't automatically, say, open Firefox on the Mozilla desktop.

So from a screen reader perspective, what's it doing to have eight virtual desktops? I'm honestly curious because I keep thinking they're an interesting idea, and then I kind of look into them, and then I can't see why I'd want to use them. But that's probably my lack of imagination, and nothing against virtual desktops.

I also don't leave lots of windows open, if I'm done with Thunderbird, for instance, I close it. I only open it up when I want to do something with email. Sometimes I'll have a reading app open and I'll go do something in Firefox and maybe open up multiple windows looking stuff up, but that's about it, and then I close Firefox when I'm done with that. Maybe that's why I can't see what they do.

I surmise this to be the case as well. I work with virtual desktops daily, sometimes  8 of them. It would be nice to have them read in the title bar rather than “explorer.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Monday, January 31, 2022 3:55 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] windows virtual desktops

 

Quentin,

The issue you mention focuses primarily on something that Juan implies has been fixed:  Lack of announcement of desktop name when moving between desktops.  He explicitly states, "When moving between desktops via ctrl+win+left/right it reads the desktop number, i.e. desktop 1, desktop 2 etc."

I'd imagine if you manually renamed the desktop(s), the name(s) you've assigned would be announced during movement between desktops.

The way I read this request is a way to just have the name of the desktop that's currently got focus announced without the need to change desktops.  I can imagine (and only imagine, as virtual desktops are "not my thing") that if you have enough of them, have been working with a number of them all day, and walk away for a while you may forget which one you were working on and just want to know which one has focus.

I read this request as being analgous to reading a window title on command, but for a desktop title instead.  I hope that Juan clarifies.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 

--

I surmise this to be the case as well. I work with virtual desktops daily, sometimes  8 of them. It would be nice to have them read in the title bar rather than “explorer.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Monday, January 31, 2022 3:55 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] windows virtual desktops

 

Quentin,

The issue you mention focuses primarily on something that Juan implies has been fixed:  Lack of announcement of desktop name when moving between desktops.  He explicitly states, "When moving between desktops via ctrl+win+left/right it reads the desktop number, i.e. desktop 1, desktop 2 etc."

I'd imagine if you manually renamed the desktop(s), the name(s) you've assigned would be announced during movement between desktops.

The way I read this request is a way to just have the name of the desktop that's currently got focus announced without the need to change desktops.  I can imagine (and only imagine, as virtual desktops are "not my thing") that if you have enough of them, have been working with a number of them all day, and walk away for a while you may forget which one you were working on and just want to know which one has focus.

I read this request as being analgous to reading a window title on command, but for a desktop title instead.  I hope that Juan clarifies.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 

Quentin,

The issue you mention focuses primarily on something that Juan implies has been fixed:  Lack of announcement of desktop name when moving between desktops.  He explicitly states, "When moving between desktops via ctrl+win+left/right it reads the desktop number, i.e. desktop 1, desktop 2 etc."

I'd imagine if you manually renamed the desktop(s), the name(s) you've assigned would be announced during movement between desktops.

The way I read this request is a way to just have the name of the desktop that's currently got focus announced without the need to change desktops.  I can imagine (and only imagine, as virtual desktops are "not my thing") that if you have enough of them, have been working with a number of them all day, and walk away for a while you may forget which one you were working on and just want to know which one has focus.

I read this request as being analgous to reading a window title on command, but for a desktop title instead.  I hope that Juan clarifies.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

Great idea. Window-Eyes used to have this feature and it was really quick and useful.

Janet

I was thinking today about a new feature that might speed up work a good deal when writing documents.  I generally don't use f7 spell check these days.  I read my messages before sending them and change flagged spelling errors, thus doing two things at once that I would do separately otherwise. 

My proposal for a new feature, which I'd like comments about in terms of demand and feasibility is this:

There could be an NVDA command that moves to the next flagged misspelled word in a document.  Even if I read a document and hear a word flagged, the cursor is almost never on the word.  Its often at the beginning of the line and the misspelled word may take a lot of movement by word to get to.  If I could hear the flag, then issue the move to command, moving to the word could be sped up a lot most of the time.   As I think about it, this adds the equivalent to what a sighted person can do now.  A word is flagged, the sighted person can immediately move to or click on it, thus placing focus on it, and either manually correct it or use the context menu to do so.  Or a sighted person can do so later by seeing the flag, clicking on it, and correcting the word.

I'm surprised this hasn't been discussed before.  I did a Google search and I didn't find a Github issue, though I didn't search Github directly.

Gene

Hi All,

I use virtual desktops a lot.  When moving between desktops via ctrl+win+left/right it reads the desktop number, i.e. desktop 1, desktop 2 etc.

Now I was wondering is it possible for NVDA to state what desktop I currently have active via the title command, ins+t?

Like Jaws does?

Any input is greatly appreciated.

Best,

Juan

Hi,

Update: Microsoft Natural Voices are retrieved from Microsoft Store. Although these voices are set to be compatible with Windows 10 Version 1809 (October 2018 Update), they are only available in build 22543 (as explained in another thread) and shown as compatible with 64-bit systems only. This actually makes sense considering that Windows 11 is a strictly a 64-bit operating system.

Regarding the theory I had: yes, what I wrote above confirms it - the third location under my consideration is a folder that stores Microsoft Store apps. If things are available from Store, chances are that data about them will be stored in this location which users cannot access (actually, yes you can but that's really beyond the scope of this forum and is quite advanced with implications). Therefore, unless proven false, I stand by my explanation that Microsoft is testing a new synthesizer engine, something I think might be of use when Microsoft says anyone (including NVDA) can utilize these voices.

Cheers,

Joseph