Date   

locked Re: Please read and consider: importance of providing exact (or almost exact) Windows version information will be helpful soon

Yeti
 

Hello Brian and All,

the need for specificity when seeking assistance
On the other hand, people with little technical understanding also seek advice from lists like this one, for whom it is not so easy to collect this information or even to filter it according to its importance.

Other screen readers - such as BAUM's COBRA - therefore had a function to collect this information and make it available on the clipboard.

This could be realized rather easily with an add-on. However, this add-on would certainly not always and everywhere be available where it was needed.

This functionality should therefore be one of the NVDA kernel.

Just my 50 cents

Ad Astra

yeti


locked Re: Please read and consider: importance of providing exact (or almost exact) Windows version information will be helpful soon

 

Speaking in my official role as group moderator, I could not agree more about the need for specificity when seeking assistance on a technical support forum, and not just this one and not just in regard to Windows.  It becomes even more critical when we're in transition periods like now where two "primary" versions of Windows coexist, 10 and 11, along with another "secondary" one, 8.1, which has relatively few users compared to the other two.

It's really easy to create a simple text file that looks something like this:

Windows 10 21H2, Build 19044
NVDA 2022.2.1
Microsoft Office 2016 | Firefox 104.0 | Chrome 104.0.5112.10

where the first two lines are your computing and screen reader environment information, and what follows is what's pertinent to the "question at hand" whether that's about Microsoft Office, or a specific NVDA Add-On, or a web browser (and it's version should be specified - available via Help, About from all of them).  That third line could be a permanent one where the software you are most frequently using, and the respective version numbers for each, are listed.

There are many instances where it is absolutely impossible to give an accurate answer without one or more of these pieces of information.  Having them stored in a small text file from which you can copy and paste them, and update them as needed, makes it easy to present that information every time it's needed.
--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard


locked Please read and consider: importance of providing exact (or almost exact) Windows version information will be helpful soon

 

Hi all,

The following applies most to Windows 11 users but I believe it applies to all of us:

If you’ve been keeping an eye on Windows 11 development, you should have heard about an upcoming feature update called Version 22H2, scheduled for public release soon. You should have also heard about a similar news on a feature update for Windows 10 named, appropriately enough, Version 22H2. These feature updates are completely different in nature, update process, and applicability.

Why do I bring up Version 22H2 for both Windows 10 and 11? For some time Microsoft has been using the term “original release” to refer to Windows 11 Version 21H2 (build 22000). If you remember from seven years ago, when Microsoft was working on the first feature update for Windows 10 (Version 1511), the original Windows 10 was labeled as “1507)’, “RTM”, and “initial version”. Back then feature updates were release once or twice a year so the confusion surrounding version information did not last long (or people can say it lasted a bit longer). But with Windows releases coming in an annual cycle, coupled with staggered approach to update availability, Windows version confusion can last longer.

Therefore, I strongly advise you to provide exact (or almost exact) Windows version you have so people using your configuration can help you better. Simply saying “I’m using Windows 11,” while it has worked for the last twelve months or so, will no longer hold true in coming weeks; there are at least three Windows 11 releases (including Insider Preview) at any given moment, and you can see why I’m strongly advising folks to provide version information (more so now as Windows Insiders subscribing to beta channel will get one of two builds). For reverence, whenever you tell me “I am running Windows 11”, I will assume the latest public release (21H2 for now, 22H2 once it is released).

There is another reason for bringing up Version 22H2 for both Windows 10 and 11: they will be using completely different update mechanism:

  • Windows 10 (build 19045): Version 22H2 is an enablement package. Although Windows Insiders don’t know what’s included in the upcoming feature update, all (or almost all) components for the feature update will be part of upcoming cumulative updates for 21H1 and 21H2.
  • Windows 11 (build 22621): it is a completely different version of Windows, not an enablement package. If you’ve upgraded from Windows 10 to 11 on compatible systems, you should remember what it was like, and same will happen with Version 22H2.

 

Among many methods for checking the exact Windows version you are using, the fastest method is About Windows dialog (Start menu, type “winver” without quotes, press Enter, and read the information provided). There are three methods that are faster: two are specific to NVDA (NVDA log and Resource Monitor add-on, respectively), one is looking for a changed menu entry in quick link menu (Windows+X) introduced in Windows 11 Version 22H2.

Speaking of Windows 11 Version 22H2: although you can use old NVDA releases, I advise waiting until NVDA 2022.3 is released before upgrading. This release includes foundations to support some upcoming features (notably console apps support improvements); but it will not be until 2022.4 (under development) that support for Windows 11 Version 22H2 sees much improvement, and I expect most of you to see 22H2 as early as late 2022 or early 2023.

Cheers,

Joseph


Re: Access to Windows 10 Games: Suggestion for compatibility update or add-on for NVDA

 

Hi,

It might be possible that achievements and calendar information is presented in a way that cannot be navigated or spoken when system focus moves. This can be tested if using Narrator and see if it announces things, and if yes, it might be time to reintroduce Solitaire app support in Windows App Essentials (too late for upcoming 22.09 release and likely not until late November; need to earn points (grades) before advancing to the next level).

As for tips and tricks, it depends on what you want to do with or without a specific app in mind, something we might as well discuss on a dedicated thread.

Cheers,

Joseph


Re: Question About Code Factory Addon Incompatibility

 

On Fri, Aug 26, 2022 at 05:38 AM, Socheat wrote:
please do a search on groups.io first.
-
And I've written a tutorial to make this much easier for those who've never done one:

Searching a Groups.io Topics Page/Archive
along with one for simply browsing and reading via the Groups.io web interface:

Browsing a Groups.io Topics Page/Archive
--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard


Re: Question About Code Factory Addon Incompatibility

Sarah k Alawami
 

It has been fixed for a while now. Go to atguys.com if you bought it there and dl it from there.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joanne Michelle Stark
Sent: Friday, August 26, 2022 12:32 AM
To: nvda@nvda.groups.io
Subject: [nvda] Question About Code Factory Addon Incompatibility

 

Good morning,

Forgive me if this has already been discussed. Out of curiosity, does anyone know if an update to this addon is being worked on? I have updated to the latest version of NVDA and am missing eloquence already and the option to switch to vocalizer Express voices. I hope they fix this soon since I had to shell out money for that.

Have a great day.


Re: Is there a way to run NVDA as a window and not a background process?

Sarah k Alawami
 

This is a different method. You will be able to capture different audio sources and if using mkv, possibly mp4, you can then use ffmpetgg to extract all tracks for post editing. I am using a plugin to do this right now in obs 27.x and it works actually quite well. I can actually find all things from this session and nvda is one of those, no window necessary. If OBS can implement looking in the system tray as well, that would be nice. Time to put a fly in their ear about that, or a bee in their bonnet?

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail list account via groups.io
Sent: Friday, August 26, 2022 12:14 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Is there a way to run NVDA as a window and not a background process?

Hmm, I actually like the way one can capture all windows audio with a program called virtual recorder. It can make demos very easy, since not only do you hear the screenreader, but the results and other sounds generated by whatever application you are using as well.
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: "Joshua Tubbs" <orin8722@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 25, 2022 8:02 PM
Subject: [nvda] Is there a way to run NVDA as a window and not a background process?


Hi all,

The reason I ask this is because OBS (open broadcaster software) beta
has a new feature to capture application-specific audio. Right now, I
can't capture NVDA and/or add it as a source because nvda.exe is
running in a background process and doesn't show up as a window.
I know Jaws has an option to send it to the tray as an option, but
does NVDA? I remember there might have been one a very long time ago.
Not really needed but this is a specific use case.
Thanks.






Re: what do you think of this NVDA suggestion?

 

Is this really an NVDA function (or insert any screen reader in place of NVDA) or a function of the Synth?

I know why screen readers give the ability to tweak the most commonly changed and pretty basic parameters, but something this advanced seems to be to be "out of scope" for any given screen reader and the province of the synth maker to give advanced editing tools and the ability to save the edited voices with names such that you can identify the ones you've made many complex tweaks for.

For myself, I don't see this as an "job for NVDA" or any other screen reader.
--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard


Re: Using Google Docs with NVDA

Nolan Darilek
 

Here are a couple issues I've had with it, would appreciate some advice if anyone has it:

* I've enabled Braille display support because my understanding is that makes things more accessible. And indeed, this does seem to use native HTML elements/attributes vs. whatever Google hand-rolled to emulate screen reader support. But I've also noticed it doesn't handle longer lines or paragraphs. It's as if speech stops partway through reading the line. And it'd be better if they just wrapped, but either they don't, or the wrapping is only visual and not accessible. Is there a fix for this? Or should I just disable Braille support?

* A lot of the hotkeys use ctrl-alt-n as a prefix, and that's the hotkey I use to restart NVDA. Can't remember if I added this myself or if it's the default. I know I can change this, but at this point ctrl-alt-n is muscle memory, and changing this for one application is going to be a lot of trouble. Is there any way to work around this? I know I can use the menus to jump to the next comment/annotation/whatever, but that's several keystrokes instead of one, and makes editing collaboratively a bit of a pain. Guessing the answer is no and I'll have to deal, but maybe there's a way to work around this that I don't know of.

I recently had a writing gig where I needed a collaborative online editor. We migrated to Markdown and a GitHub PR-based workflow, but that's not ideal for a variety of reasons. If I can figure out how to make Docs workable, it'd likely be a better option.

Thanks for any tips.

On 8/24/2022 9:14 PM, Nimer Jaber wrote:

It is accessible and works pretty well. I use it daily. Please ask if you run into issues.

On Wed, Aug 24, 2022 at 7:02 PM Kenny Cheung <kennycheung0@...> wrote:
Hi,

I found out that for my creative writing class, we'll be using google
dox. I'm wondering, how accessible is that with NVDA?

Kenny








--
Best,

Nimer Jaber

Check out and subscribe to BlindTechAdventures in podcast audio form on YouTube for the latest happenings in tech.

You can follow @nimerjaber on Twitter for the latest technology news.

Thank you, and have a great day!


what do you think of this NVDA suggestion?

Josh Kennedy
 

I posted the following issue on NVDA github and I think it’s a good idea. So what do you all think?

 

First the link to the issue then below is the text of the issue.

 

https://github.com/nvaccess/nvda/issues/14074

 

 

In the old NV-speech-player NvDA addon, you could adjust many many different speech parameters. Therefore so the user can further tweak ESpeak, especially its Klatt voices, could you please create an advanced speech dialog with a warning checkbox similar to the warning checkbox in the normal advanced settings dialog box? The advanced speech settings dialog would let the advanced user change by using ssliders or edit boxes, many many more parameters, virtually every single parameter of ESpeak's normal formants and especially its Klatt formants. radio buttons would let you choose between changing Klatt parameters or normal parameters and then appropriate parameter settings would appear when you tab to the main settings area. In this advanced dialog, all possible ESpeak parameters could be changed and modified--including all of its tunes or intonation statements. You would hear the changes as you make them. When done, you could give your custom changes a name, save them in either the older ESpeak sapi5 format or the new ESpeak-ng format and then share them with other NVDA users. A restore button would reset all settings back to normal in case you really mess up. Want to adjust ESpeak to inflect like Keynote gold? eloquence? or something of your own creation? no problem. Save a copy of your changes in both the older ESpeak format and another copy in the newer ESpeak-ng format then share with other users. I am tired of people complaining about ESpeak... ok so give us an advanced speech dialog where we can tweak and change to our heart's content and share our changes with older sapi5 ESpeak users and the newer ESpeak-ng users. And since ESpeak runs on android such variants could be imported to the ESpeak of other platforms maybe. not sure about that one though. Please let us tweak and change very advanced ESpeak parameters and save changes with an advanced speech dialog box everything including intonation tunes statements.

 


Re: Using Google Docs with NVDA

 

On Fri, Aug 26, 2022 at 03:11 AM, Brian's Mail list account wrote:
ER, Brian, now who is ranting?
-
I was, and make no bones about it.  This plaint is way, way, way past it's expiration date.  But, as you've noted, this has now been moved to a topic on the Chat Subgroup.

I would be far from the only person who would be eternally grateful if they never heard a single complaint about the ribbon interface again.  Complaining about it, rather than having basic skills if not complete mastery of it, 15 years after its introduction is the very definition of the phrase, "pissing into the wind."  There are many among us who are tired of the "spray" we get hit with as a result.
--

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

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard


Re: Using Google Docs with NVDA

Gene
 

If you had learned ribbons first and had good and detailed instruction, you might be saying the same thing about menus. 

I don't recall if you worked with my tutorial about ribbons.  It may be that your individual brain has more problems conceptualizing ribbons but it may simply be that you didn't have good instruction in them. 

It doesn't matter what a lot of other people think in this instance because we have no idea why they think it.  Do they really find ribbons more difficult because they do or because they haven't had good instruction in them. 

Gene

On 8/26/2022 2:11 AM, Brian's Mail list account via groups.io wrote:

ER, Brian, now who is ranting?
I do feel along with a lot of others, that its nowhere near as intuitive as the old menu structure, but that is all I shall say.I've carried the discussion to the chat group now anyway.
Brian



Re: Query regarding NVDA Logging Level

Quentin Christensen
 

I haven't found it to slow anything down - if you look at how much it records, yes it can record a lot to wade through if you are using debug level and looking back over several hours - but in scheme of modern computers, I've never noticed a slowdown from a higher log level.  The main reason we don't recommend leaving it on any of the higher settings is just privacy so you don't have anything stored in the log.

On Fri, Aug 26, 2022 at 5:08 PM Brian's Mail list account via groups.io <bglists=blueyonder.co.uk@groups.io> wrote:

I think its more important to only set it high on a new version of a beta or
alpha on a machine. I have often wondered though if it actually slows down
any operations when set high?
 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: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 25, 2022 7:54 AM
Subject: Re: [nvda] Query regarding NVDA login level


They're "Log" level, rather than login level - they determine the amount of
information recorded in your NVDA log file.  You can find the log in your
%temp% folder (note the percent signs either side of the word temp).

The higher the level (with debug being the highest), the more amount of
information is recorded in the log.  We don't recommend leaving it set to a
high level generally, just because of the amount of extra information it
records, particularly potentially personal information if it is recording
what you type and what it reads.  Note that no matter what level the log is
set to, nothing is ever done with it - ie it is never sent anywhere unless
you attach it to an email etc (which I might ask you to do for a bug I
can't replicate).

Kind regards

Quentin.

On Thu, Aug 25, 2022 at 2:48 PM Kakarla Nageswaraiah <
nageswara1982@...> wrote:

> Dear all,
>
> I'm a full time user of NVDA.
>
> I'd like to know about different options of login level under
> Preferences > Settings > General.
>
> What is the difference between Info, Debug warning, Input/Output and
> Debug?
>
> Kindly elaborate.
>
> Thanks and regards.
>
> --
> కాకర్ల నాగేశ్వరయ్య
>
> K. Nageswaraiah
>
>
>
>
>
>

--
Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>













--
Quentin Christensen
Training and Support Manager


Re: NVDA 2022.2.2 released

Quentin Christensen
 

I came back from dinner and found my information was out of date :)


The main change, like with 2022.2.2, is fixing the input gestures bug caused by the security patch in the previous version (apologies for that!)

It's just the official post which is delayed.  If you are running Beta 3, it will prompt to update in due course.

Kind regards

Quentin.

On Fri, Aug 26, 2022 at 7:45 PM <gbmagoo@...> wrote:

Yes I would like this direct link also thanks

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Afik Souffir
Sent: Friday, August 26, 2022 02:44
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2022.2.2 released

 

Can you send the direct link for the latest beta?

 

Thanks,

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Friday, August 26, 2022 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2022.2.2 released

 

Small update - there was a problem building the new beta, so that will likely come out Monday now.  Those running Beta 3 will still be prompted to "update" to 2022.2.2 (because the build date is newer), just ignore that invitation if you want to stay on beta.

 

Quentin.

 

On Fri, Aug 26, 2022 at 5:09 PM Quentin Christensen via groups.io <quentin=nvaccess.org@groups.io> wrote:

Fantastic,

 

Thanks Sergey!

 

Also a quick note for anyone running the beta - there will be a corresponding new beta with the same fix in it shortly - however, if you check for updates currently from NVDA 2022.3 beta 3, it will offer 2022.2.2 as an "update" (so hang time, we'll be with you shortly).

 

Kind regards

 

Quentin.

 

On Fri, Aug 26, 2022 at 4:57 PM Sergey Fleytin <fleytin@...> wrote:

Hi Quentin.

 

The gestures bug is fixed indeed!

 

Thanks!

 

 

26.08.2022 9:06, Quentin Christensen пишет:

Hi everyone,

 

Another release!  All the 2s!  NVDA 2022.2.2 is now available.  This patch release fixes a bug introduced in 2022.2.1 with input gestures.  Please note that the "What's new" text has not been translated.  The correct current version can be found in “About NVDA” from the Help menu. Download & more info: https://www.nvaccess.org/post/nvda-2022-2-2/

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 


 

--

Quentin Christensen
Training and Support Manager

 


 

--

Quentin Christensen
Training and Support Manager

 



--
Quentin Christensen
Training and Support Manager


Re: NVDA 2022.2.2 released

gbmagoo@...
 

Yes I would like this direct link also thanks

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Afik Souffir
Sent: Friday, August 26, 2022 02:44
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2022.2.2 released

 

Can you send the direct link for the latest beta?

 

Thanks,

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Friday, August 26, 2022 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2022.2.2 released

 

Small update - there was a problem building the new beta, so that will likely come out Monday now.  Those running Beta 3 will still be prompted to "update" to 2022.2.2 (because the build date is newer), just ignore that invitation if you want to stay on beta.

 

Quentin.

 

On Fri, Aug 26, 2022 at 5:09 PM Quentin Christensen via groups.io <quentin=nvaccess.org@groups.io> wrote:

Fantastic,

 

Thanks Sergey!

 

Also a quick note for anyone running the beta - there will be a corresponding new beta with the same fix in it shortly - however, if you check for updates currently from NVDA 2022.3 beta 3, it will offer 2022.2.2 as an "update" (so hang time, we'll be with you shortly).

 

Kind regards

 

Quentin.

 

On Fri, Aug 26, 2022 at 4:57 PM Sergey Fleytin <fleytin@...> wrote:

Hi Quentin.

 

The gestures bug is fixed indeed!

 

Thanks!

 

 

26.08.2022 9:06, Quentin Christensen пишет:

Hi everyone,

 

Another release!  All the 2s!  NVDA 2022.2.2 is now available.  This patch release fixes a bug introduced in 2022.2.1 with input gestures.  Please note that the "What's new" text has not been translated.  The correct current version can be found in “About NVDA” from the Help menu. Download & more info: https://www.nvaccess.org/post/nvda-2022-2-2/

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 


 

--

Quentin Christensen
Training and Support Manager

 


 

--

Quentin Christensen
Training and Support Manager

 


Re: NVDA 2022.2.2 released

Afik Souffir <afik.souffir@...>
 

Can you send the direct link for the latest beta?

 

Thanks,

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Friday, August 26, 2022 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2022.2.2 released

 

Small update - there was a problem building the new beta, so that will likely come out Monday now.  Those running Beta 3 will still be prompted to "update" to 2022.2.2 (because the build date is newer), just ignore that invitation if you want to stay on beta.

 

Quentin.

 

On Fri, Aug 26, 2022 at 5:09 PM Quentin Christensen via groups.io <quentin=nvaccess.org@groups.io> wrote:

Fantastic,

 

Thanks Sergey!

 

Also a quick note for anyone running the beta - there will be a corresponding new beta with the same fix in it shortly - however, if you check for updates currently from NVDA 2022.3 beta 3, it will offer 2022.2.2 as an "update" (so hang time, we'll be with you shortly).

 

Kind regards

 

Quentin.

 

On Fri, Aug 26, 2022 at 4:57 PM Sergey Fleytin <fleytin@...> wrote:

Hi Quentin.

 

The gestures bug is fixed indeed!

 

Thanks!

 

 

26.08.2022 9:06, Quentin Christensen пишет:

Hi everyone,

 

Another release!  All the 2s!  NVDA 2022.2.2 is now available.  This patch release fixes a bug introduced in 2022.2.1 with input gestures.  Please note that the "What's new" text has not been translated.  The correct current version can be found in “About NVDA” from the Help menu. Download & more info: https://www.nvaccess.org/post/nvda-2022-2-2/

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 


 

--

Quentin Christensen
Training and Support Manager

 


 

--

Quentin Christensen
Training and Support Manager

 


Re: NVDA 2022.2.2 released

Quentin Christensen
 

Small update - there was a problem building the new beta, so that will likely come out Monday now.  Those running Beta 3 will still be prompted to "update" to 2022.2.2 (because the build date is newer), just ignore that invitation if you want to stay on beta.

Quentin.

On Fri, Aug 26, 2022 at 5:09 PM Quentin Christensen via groups.io <quentin=nvaccess.org@groups.io> wrote:
Fantastic,

Thanks Sergey!

Also a quick note for anyone running the beta - there will be a corresponding new beta with the same fix in it shortly - however, if you check for updates currently from NVDA 2022.3 beta 3, it will offer 2022.2.2 as an "update" (so hang time, we'll be with you shortly).

Kind regards

Quentin.

On Fri, Aug 26, 2022 at 4:57 PM Sergey Fleytin <fleytin@...> wrote:

Hi Quentin.


The gestures bug is fixed indeed!


Thanks!



26.08.2022 9:06, Quentin Christensen пишет:
Hi everyone,

Another release!  All the 2s!  NVDA 2022.2.2 is now available.  This patch release fixes a bug introduced in 2022.2.1 with input gestures.  Please note that the "What's new" text has not been translated.  The correct current version can be found in “About NVDA” from the Help menu. Download & more info: https://www.nvaccess.org/post/nvda-2022-2-2/

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager



--
Quentin Christensen
Training and Support Manager



--
Quentin Christensen
Training and Support Manager


Re: Question About Code Factory Addon Incompatibility

Socheat
 

Hi

The add-on is already updated. Also, a friendly suggestion, before posting to the mailing list, please do a search on groups.io first. This topic has been discussed recently.


On Fri, Aug 26, 2022 at 2:31 PM Joanne Michelle Stark <Suzannegirl25@...> wrote:

Good morning,

Forgive me if this has already been discussed. Out of curiosity, does anyone know if an update to this addon is being worked on? I have updated to the latest version of NVDA and am missing eloquence already and the option to switch to vocalizer Express voices. I hope they fix this soon since I had to shell out money for that.

Have a great day.


Question About Code Factory Addon Incompatibility

Joanne Michelle Stark
 

Good morning,

Forgive me if this has already been discussed. Out of curiosity, does anyone know if an update to this addon is being worked on? I have updated to the latest version of NVDA and am missing eloquence already and the option to switch to vocalizer Express voices. I hope they fix this soon since I had to shell out money for that.

Have a great day.


Re: Is there a way to run NVDA as a window and not a background process?

Brian's Mail list account
 

Which reminds me, is it a bug then that sometimes ends up at boot up with a window open that if you close it, you also close nvda?
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: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Friday, August 26, 2022 12:53 AM
Subject: Re: [nvda] Is there a way to run NVDA as a window and not a background process?


Hi,

Back wqhen NVDA's GUI was first implemented (2007 or so I believe), NVDA had its own window that was always visible (named "NVDA user interface"). To minimize distraction, NVDA eventualy became an icon in system tray. Narrator follows this change as well.

Cheers,

Joseph