Date   

Re: Shortcut commands stopping working in NVDA

 

On Wed, Jul 21, 2021 at 06:54 PM, Gene wrote:
If it turns out to be keys getting stuck, that may lead to a solution.
-
Gene,

Before I say what I'm about to say, I want to preface it with this contribution is greatly appreciated, at least by me.  This is a great diagnostic to undertake.

With that being said, if the root cause were traced to literal sticky keys, the solution is getting a new keyboard.  There is nothing that the developers of NVDA could or should do about sticking keyboard keys.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Shortcut commands stopping working in NVDA

Gene
 

Occasionally, a problem where NVDA shortcut commands such as read title bar, open menus, etc. stop working has been discussed here.  I may have found out what is actually going on and it may either eliminate or almost fully eliminate the need to unload, then run NVDA again.
 
It appears to me that a key is getting stuck.  When this happens, try pressing the left shift key, then the right shift key quickly perhaps five or six times each.  Then see if the commands work again. 
 
Caution: It used to be and probably still is the default that if you press either shift something like five times, it will turn on something.  I don’t recall if it is some sort of sounds Windows will make when certain keys are pressed or sticky keys.  At any rate, if you haven’t turned off this behavior, don’t press the shift five times.  Try three or four. 
 
I’ve just been trying this recently.  I don’t have this happen enough to see if the same key, for example, one of the shift keys, or another key, such as either control, either alt, or the NVDA key, gets stuck in new occurrences or if the same key gets stuck and no others.  Experimentation by people will answer that question. 
 
If it turns out to be keys getting stuck, that may lead to a solution. 
 
Gene
 


Introducing Event Tracker, an add-on to track and record information on events #addonrelease

 

Hi all,

Yes, a brand new add-on, and most likely my last one for now:

A new add-on designed for developers and power users, called Event Tracker is now available:

Event Tracker (nvda-project.org)

An event is raised when things happen, such as typing characters, moving system focus, and when notifications are announced. Event Tracker will track these events and will log information such as the control where the event came from, its name and role, app module, and information specific to accessibility API’s such as MSAA properties. As this is an add-on designed for developers and power users, it is not really recommended for beginners, and in order to use the add-on, you must be running NVDA in debug logging mode.

Cheers,

Joseph


Re: Notice for users of Joseph Lee's add-ons: what's new in version 21.08, an important announcement or two regarding support for NVDA changes going forward

anthony borg
 

Many thanks Joseph for your great help and support you are giving us.

 

Regards

 

Anthony

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: 21 July 2021 07:06
To: nvda@nvda.groups.io
Subject: [nvda] Notice for users of Joseph Lee's add-ons: what's new in version 21.08, an important announcement or two regarding support for NVDA changes going forward

 

Hello NvDA users,

First, I hope you are staying safe and healthy in the midst of events around the world, namely the ongoing pandemic.

Second, I and several folks here are in contact with NvDA add-ons community regarding add-ons you know and love. I’m delighted to announce that, as of this moment, 70 percent of add-ons hosted on community add-ons website are showing as compatible with NVDA 2021.1. I know there are more add-ons out there, and more of these are becoming compatible as time passes. As was stated many times, the actual people to contact regarding add-ons is the author of these add-ons, not NV Access, and authors were encouraged to update incompatible add-ons as soon as possible.

 

Onto the matter at hand:

Heads up if you are using any of my add-ons (Add-on Updater, Control Usage Assistant, Enhanced Touch Gestures, GoldWave, Resource Monitor, StationPlaylist, Windows App Essentials): version 21.08 updates are being prepared (scheduled for next week). Most add-ons include feature updates, while others include localization updates from translators around the world. But most importantly, a major change in NVDA is coming which will affect most of my add-ons, and the time has come to start letting go of most add-ons to focus on school.

What’s new in version 21.08? For starters, Windows 11 support. Enhanced Touch Gestures, Resource Monitor, and Windows App Essentials will include support for Windows 11. The biggest changes were made in Windows App Essentials, followed by Resource Monitor, the former to work around current Windows 11 preview issues, the latter to recognize Windows 11 builds properly. A bonus for Enhanced Touch Gestures users: current and upcoming add-on releases will work beautifully on Windows 11. Note that for at least Windows App Essentials, Windows 11 support is experimental/in preview and things can change without notice (I’m planning a follow-up release in late August that will update the add-on to support the state of Windows 11 preview then).

Second, localization updates. These include all add-ons. Several add-ons didn’t have localization updates for almost half a year, while others include recent changes. Note that Add-on Updater is not amongst these at this time.

Third (and most importantly and will get lengthy)), preparing to respond to changes being introduced to NVDA. One of the biggest features in Python 3 series is support for enumerations (or enums for short). An enumeration is a collection of values and flags that are easily grouped and identifiable. For example, suppose you are defining colors and decide to use integers to represent colors such as “blue” (0), “red” (1), “green” (2) and so on, housed inside a “colors” collection. In the past, you had to remember which color corresponds to which integer, but with enumerations, when you say “colors.Red”, Python will know what you are talking about (integer 1). This makes the program source code easier to read.

In the NVDA world, there are places in NVDA screen reader source code that resemble a collection of flags and constants. The best known example is a module called “control types” that include definitions of control roles and states. The roles and states collection is so important that NVDA itself and many add-ons use this module as a backbone for their proper operation, including recognizing specific controls in apps, reacting to state changes such as radio buttons being checked, and even providing user-level help (Control Usage Assistant). The current code (NVDA 2021.1) is compatible with both Python 2 and 3, but NV Access and contributors felt modernization should be attempted, specifically using facilities from Python 3 in more places.

Last year, NVDA moved from Python 2 to Python 3, the former without enumerations, the latter including it as part of an “enum” module. To study the impact of using enumerations to represent values and constants, NV Access introduced enums in a limited scale in NVDA 2020.1 (May 2020), specifically to represent speech output reasons (converted from a collection of integers to an enumeration in 2020.1). It turned out several add-ons (including StationPlaylist) used the old speech style, and since NVDA 2021.1 removed old style speech output reason collection in favor of enumeration, add-ons were modified recently to take advantage of the new style (that’s one of the reasons why, for some add-ons, you can’t modify manifests alone).

In the next version of NVDA (2021.2), enumeration usage is expanded to cover control roles and states (these are now enumerations, not constants anymore), and this work is termed “control types refactor”. Because the new enumerations are here to stay, NV Access promised old style (constants) will remain until NVDA 2022.1 (the next backwards incompatible release) is released to the public; until then, add-ons are welcome to use old and new styles to detect control roles and states.

So what does this “control types refactor” got to do with Joseph Lee’s add-ons? Control types refactor affects add-ons using control types module contents, including Control Usage Assistant, Enhanced Touch Gestures, GoldWave, StationPlaylist, and Windows App Essentials. At least until NVDA 2022.1 is released, the old control roles and states style will be kept, so it won’t affect my add-ons. However, after looking at the scale of control types refactor, coupled with impact of graduate school on add-on maintenance work, I decided to let my add-ons work with new (enumeration) style sooner than later. Therefore;

I hereby announce that version 21.08 of my add-ons will be the last releases to support NVDA 2021.1 or earlier, with the next releases exclusively supporting NVDA 2021.2 or later. This is so that I can spend more time studying and eventually easing add-on maintenance.

Not all add-ons are impacted by this announcement at the moment:

  • Affected add-ons: Control Usage Assistant, Enhanced Touch Gestures, GoldWave, StationPlaylist
  • Not affected but a separate compatibility announcement forthcoming: Resource Monitor
  • Affected by things in addition to control types refactor: Windows App Essentials due to Windows 11 being a preview release at the moment

Add-on Updater is not affected at this time.

Next steps:

  1. For affected add-ons, there will be no updates between 21.08 (next week) and the week during which NVDA 2021.2 release candidate is announced. The actual releases requiring NVDA 2021.2 will be posted at least two days after NVDA 2021.2 is released to the general public. This is done so you can focus on other add-ons.
  2. Windows App Essentials will receive updates while Windows 11 is being finalized. This is so that the add-on and NVDA can respond to late changes.
  3. To make life easier, there will be no updates to Resource Monitor between 21.08 and the day NVDA 2021.2 is released to everyone. Again this is so that I can focus on graduate studies before releasing a version of Resource Monitor requiring newer NVDA releases.
  4. Add-on Updater is on standby – that is, localization updates can be released anytime.

 

As a volunteer add-on author and maintainer with NVDA code contribution experience, I take add-on maintenance seriously. I feel it is important to tell you what’s going on so you can prepare accordingly, especially since what I just announced is based on changes to NVDA that will affect many add-ons. As long as I maintain these add-ons, I will do my best to make add-ons work with newer NVDA releases and make them compatible the day new NVDA versions show up when you check for updates.

 

Thanks. Hope this helps.

Cheers,

Joseph


Welcome to the NVDA Community Add-ons website - Event Tracker #nvdaaddonsfeed

nvda@nvda.groups.io Integration <nvda@...>
 

Event Tracker

  • Author: Joseph Lee
  • Download stable version
  • NVDA compatibility: 2021.1 and beyond

This add-on outputs information about objects for which events were fired. Properties recorded in debug log mode include object type, name, role, event, app module, and accessibility API specific information such as accName for IAccessible object and Automation Id for UIA objects.

Notes:

  • This add-on is designed for developers and power users needing to track events coming from apps and various controls.
  • In order to use the add-on, NVDA must be logging in debug mode (configured from general settings/logging level, or restart with debug logging enabled).
  • It might be possible that add-ons loaded earlier than Event Tracker may not pass on the event to other add-ons, including Event Tracker. If this happens, Event Tracker will not be able to log events.
  • Events are handled from global plugins, app modules, tree interceptors, and NVDA objects, in that order.

Events and their information

The following events are tracked and recorded:

  • Focus manipulation: gain focus, lose focus, focus entered, foreground
  • Changes: name, value, state, description, live region
  • UIA events: element selected, item status, controller for, notification, tooltip open, window open, text change

For each event, the following information will be recorded:

  • Event name
  • Object
  • Object name
  • Object role
  • Object value or state depending on events
  • App module
  • For IAccessible objects: acc name, child ID
  • For UIA objects: Automation Id, class name, notification properties if recording notification event information

Version 21.07

  • Initial release.


NVDA 2021.1 and add-ons: more add-on updates #addonrelease

 

Hello all,

More add-ons were updated to support NVDA 2021.1. Among these are OCR, Switch Synth, and Extended Winamp. Just like we did for the last three years, please check for updates from Add-on Updater (some of you should have received a Windows 10/11 notification about add-on updates by now).

By the way, a new add-on from yours truly is on its way…

Cheers,

Joseph


Re: Com Registration fixing and narrator

mk360
 

I sent you a log privately. Please, I don't know whats the bug for NVDA, I preffer win 10 actually, and I can help testing whatever you need, but I need windows 7 for my work :(.

El 20/07/2021 a las 23:54, Quentin Christensen escribió:

If you turn off Narrator on the login screen, does it come back next time?


I haven't encountered the issue, and we'd need a bit more info to try to investigate (such as Windows & NVDA versions, etc, and ideally a debug log from running the COM registration tool - though not sure if it would show anything) - if you'd like to investigate a bit more, after fixing it and restarting to confirm, if you then ran the COM registration tool again it would be interesting to see if it did the same thing.

Regards

Quentin.

On Wed, Jul 21, 2021 at 10:38 AM mk360 <mk.seventhson@...> wrote:
Hi,

I'm having a problem with com registration fixing and narrator. I
executed the tool under Windows 7 and now Narrator starts on secure
screens, what can I do? because when it starts I can't use NVDA and is
very disturbing.

Thanks,

mk.








--
Quentin Christensen
Training and Support Manager


Notice for users of Joseph Lee's add-ons: what's new in version 21.08, an important announcement or two regarding support for NVDA changes going forward

 
Edited

Hello NvDA users,

First, I hope you are staying safe and healthy in the midst of events around the world, namely the ongoing pandemic.

Second, I and several folks here are in contact with NvDA add-ons community regarding add-ons you know and love. I’m delighted to announce that, as of this moment, 70 percent of add-ons hosted on community add-ons website are showing as compatible with NVDA 2021.1. I know there are more add-ons out there, and more of these are becoming compatible as time passes. As was stated many times, the actual people to contact regarding add-ons is the author of these add-ons, not NV Access, and authors were encouraged to update incompatible add-ons as soon as possible.

 

Onto the matter at hand:

Heads up if you are using any of my add-ons (Add-on Updater, Control Usage Assistant, Enhanced Touch Gestures, GoldWave, Resource Monitor, StationPlaylist, Windows App Essentials): version 21.08 updates are being prepared (scheduled for next week). Most add-ons include feature updates, while others include localization updates from translators around the world. But most importantly, a major change in NVDA is coming which will affect most of my add-ons, and the time has come to start letting go of most add-ons to focus on school.

What’s new in version 21.08? For starters, Windows 11 support. Enhanced Touch Gestures, Resource Monitor, and Windows App Essentials will include support for Windows 11. The biggest changes were made in Windows App Essentials, followed by Resource Monitor, the former to work around current Windows 11 preview issues, the latter to recognize Windows 11 builds properly. A bonus for Enhanced Touch Gestures users: current and upcoming add-on releases will work beautifully on Windows 11. Note that for at least Windows App Essentials, Windows 11 support is experimental/in preview and things can change without notice (I’m planning a follow-up release in late August that will update the add-on to support the state of Windows 11 preview then).

Second, localization updates. These include all add-ons. Several add-ons didn’t have localization updates for almost half a year, while others include recent changes. Note that Add-on Updater is not amongst these at this time.

Third (and most importantly and will get lengthy)), preparing to respond to changes being introduced to NVDA. One of the biggest features in Python 3 series is support for enumerations (or enums for short). An enumeration is a collection of values and flags that are easily grouped and identifiable. For example, suppose you are defining colors and decide to use integers to represent colors such as “blue” (0), “red” (1), “green” (2) and so on, housed inside a “colors” collection. In the past, you had to remember which color corresponds to which integer, but with enumerations, when you say “colors.Red”, Python will know what you are talking about (integer 1). This makes the program source code easier to read.

In the NVDA world, there are places in NVDA screen reader source code that resemble a collection of flags and constants. The best known example is a module called “control types” that include definitions of control roles and states. The roles and states collection is so important that NVDA itself and many add-ons use this module as a backbone for their proper operation, including recognizing specific controls in apps, reacting to state changes such as radio buttons being checked, and even providing user-level help (Control Usage Assistant). The current code (NVDA 2021.1) is compatible with both Python 2 and 3, but NV Access and contributors felt modernization should be attempted, specifically using facilities from Python 3 in more places.

Last year, NVDA moved from Python 2 to Python 3, the former without enumerations, the latter including it as part of an “enum” module. To study the impact of using enumerations to represent values and constants, NV Access introduced enums in a limited scale in NVDA 2020.1 (May 2020), specifically to represent speech output reasons (converted from a collection of integers to an enumeration in 2020.1). It turned out several add-ons (including StationPlaylist) used the old speech style, and since NVDA 2021.1 removed old style speech output reason collection in favor of enumeration, add-ons were modified recently to take advantage of the new style (that’s one of the reasons why, for some add-ons, you can’t modify manifests alone).

In the next version of NVDA (2021.2), enumeration usage is expanded to cover control roles and states (these are now enumerations, not constants anymore), and this work is termed “control types refactor”. Because the new enumerations are here to stay, NV Access promised old style (constants) will remain until NVDA 2022.1 (the next backwards incompatible release) is released to the public; until then, add-ons are welcome to use old and new styles to detect control roles and states.

So what does this “control types refactor” got to do with Joseph Lee’s add-ons? Control types refactor affects add-ons using control types module contents, including Control Usage Assistant, Enhanced Touch Gestures, GoldWave, StationPlaylist, and Windows App Essentials. At least until NVDA 2022.1 is released, the old control roles and states style will be kept, so it won’t affect my add-ons. However, after looking at the scale of control types refactor, coupled with impact of graduate school on add-on maintenance work, I decided to let my add-ons work with new (enumeration) style sooner than later. Therefore:

I hereby announce that version 21.08 of my add-ons will be the last releases to support NVDA 2021.1 or earlier, with the next releases exclusively supporting NVDA 2021.2 or later. This is so that I can spend more time studying and eventually easing add-on maintenance.

Not all add-ons are impacted by this announcement at the moment:

  • Affected add-ons: Control Usage Assistant, Enhanced Touch Gestures, GoldWave, StationPlaylist
  • Not affected but a separate compatibility announcement forthcoming: Resource Monitor
  • Affected by things in addition to control types refactor: Windows App Essentials due to Windows 11 being a preview release at the moment

Add-on Updater is not affected at this time.

Next steps:

  1. For affected add-ons, there will be no updates between 21.08 (next week) and the week during which NVDA 2021.2 release candidate is announced. The actual releases requiring NVDA 2021.2 will be posted at least two days after NVDA 2021.2 is released to the general public. This is done so you can focus on other add-ons.
  2. Windows App Essentials will receive updates while Windows 11 is being finalized. This is so that the add-on and NVDA can respond to late changes.
  3. To make life easier, there will be no updates to Resource Monitor between 21.08 and the day NVDA 2021.2 is released to everyone. Again this is so that I can focus on graduate studies before releasing a version of Resource Monitor requiring newer NVDA releases.
  4. Add-on Updater is on standby – that is, localization updates can be released anytime.


Update: Event Tracker is affected by control types refactor, and a version to be released later this year will require NvDA 2021.2 and later also.

As a volunteer add-on author and maintainer with NVDA code contribution experience, I take add-on maintenance seriously. I feel it is important to tell you what’s going on so you can prepare accordingly, especially since what I just announced is based on changes to NVDA that will affect many add-ons. As long as I maintain these add-ons, I will do my best to make add-ons work with newer NVDA releases and make them compatible the day new NVDA versions show up when you check for updates.

 

Thanks. Hope this helps.

Cheers,

Joseph


Re: Problem with having Admin Rights under UAC when using NVDA Remote

Jelal Bairamoglou
 


I removed all items from the following path: %HomeDrive%\Program Files (x86)\NVDA\systemConfig
I copied all items from the following path
%AppData%\nvda
Does not work properly as with previous addon.
The problem occurred after the new upgrade: remote-2.4.nvda-addon.

On 21/7/2021 1:21 π.μ., Carlos Esteban Martínez Macías via groups.io wrote:

Hi all.

You can test disable addons, but led enabled NVDA Remote and if you want, a synth Driver and another important addon for you, copy again the options for secure screens and go back to enable all the addons for your install copy. In some cases, this is the solution for this problems, but depend of your NVDA copy.

Regards.

 

 

Carlos Esteban Martínez Macías.

Soporte a usuarios, comunidad de NVDA en español.

Web www.nvda.es

Experto certificado en NVDA

 

De: Jelal Bairamoglou
Enviado: lunes, 19 de julio de 2021 10:43
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] Problem with having Admin Rights under UAC when using NVDA Remote

 

 

I have checked this for both computers and does not work.

They all worked all the problem occurred after the remote upgrade.

 

On 19/7/2021 6:43 π.μ., George McCoy wrote:

> I read, in the first iteration documentation that UaC works if both

> computers have NVDA set to speak at the logon screen. I have several

> clients whose systems are set up that way and I have no issues with UAC.

> George

>

 

 

 

 

 


--

Músico (pianista) y ayuda a usuarios ciegos y con discapacidad visual en el uso de lectores de pantalla y tecnología. Experto certificado en el lector de pantalla NVDA.

Musician (pianist) and help to the blind people and with visual disability in use of screen readers and technology. Certified expert in the screen reader NVDA.


Re: Com Registration fixing and narrator

Quentin Christensen
 

If you turn off Narrator on the login screen, does it come back next time?


I haven't encountered the issue, and we'd need a bit more info to try to investigate (such as Windows & NVDA versions, etc, and ideally a debug log from running the COM registration tool - though not sure if it would show anything) - if you'd like to investigate a bit more, after fixing it and restarting to confirm, if you then ran the COM registration tool again it would be interesting to see if it did the same thing.

Regards

Quentin.

On Wed, Jul 21, 2021 at 10:38 AM mk360 <mk.seventhson@...> wrote:
Hi,

I'm having a problem with com registration fixing and narrator. I
executed the tool under Windows 7 and now Narrator starts on secure
screens, what can I do? because when it starts I can't use NVDA and is
very disturbing.

Thanks,

mk.








--
Quentin Christensen
Training and Support Manager


Com Registration fixing and narrator

mk360
 

Hi,

I'm having a problem with com registration fixing and narrator. I executed the tool under Windows 7 and now Narrator starts on secure screens, what can I do? because when it starts I can't use NVDA and is very disturbing.

Thanks,

mk.


Re: Problem with having Admin Rights under UAC when using NVDA Remote

Carlos Esteban Martínez Macías
 

Hi all.

You can test disable addons, but led enabled NVDA Remote and if you want, a synth Driver and another important addon for you, copy again the options for secure screens and go back to enable all the addons for your install copy. In some cases, this is the solution for this problems, but depend of your NVDA copy.

Regards.

 

 

Carlos Esteban Martínez Macías.

Soporte a usuarios, comunidad de NVDA en español.

Web www.nvda.es

Experto certificado en NVDA

 

De: Jelal Bairamoglou
Enviado: lunes, 19 de julio de 2021 10:43
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] Problem with having Admin Rights under UAC when using NVDA Remote

 

 

I have checked this for both computers and does not work.

They all worked all the problem occurred after the remote upgrade.

 

On 19/7/2021 6:43 π.μ., George McCoy wrote:

> I read, in the first iteration documentation that UaC works if both

> computers have NVDA set to speak at the logon screen. I have several

> clients whose systems are set up that way and I have no issues with UAC.

> George

>

 

 

 

 

 


--

Músico (pianista) y ayuda a usuarios ciegos y con discapacidad visual en el uso de lectores de pantalla y tecnología. Experto certificado en el lector de pantalla NVDA.

Musician (pianist) and help to the blind people and with visual disability in use of screen readers and technology. Certified expert in the screen reader NVDA.


Re: Adding more add-ons to the core

Sarah k Alawami
 

Actually he said he never said that, I think that is just something someone made up.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Curtis Delzer
Sent: Tuesday, July 20, 2021 8:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Adding more add-ons to the core

and, wasn't it Bill Gates who said that "640K should be good enough for anybody?"

Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@...

On 7/19/2021 3:29 PM, Brian Vogel wrote:
On Mon, Jul 19, 2021 at 06:18 PM, Arlene wrote:

I’ve had this computer for over 2 years and its starting to slow down.

-
And? This is:

1. Expected, at least to some extent, as any machine becomes more
used and, often, more stressed with new software.

2. Is directly dependent on the hardware, operating system(s), and
software.

I'm not saying you did this, but is an example of why a statement like
yours really doesn't mean much without context, but if you buy a $200
machine with an Atom or Celeron class processor, it's actually at its
maximum load in the Windows 10 era doing very, very little indeed. It
will slow down very quickly.

It's all about demands and capacities. The higher your demands, the
greater the capacities of the hardware needs to be. And no $400
computer will come close to the performance, or longevity, of an $800
to
$1000 machine. While there's not a perfect relationship between
higher dollar (or insert your unit of currency here) and higher
performance, there is a direct one. And having processing power
"breathing room" as well as sufficient RAM are both really critical to
minimizing the amount of slowing down as time goes on.

The operating system is irrelevant. The technical specs of your
hardware are. Windows 10 can, and does, run beautifully on a great
deal of late Windows 7 era hardware that was higher end when produced.
And it, conversely, runs poorly on hardware that "meets the minimum
specifications" and not much more.

And even the very best, and most powerful, hardware will slow down
with age, and that's mostly because of the "detritus of use" building
up on the operating system side of things. Most often, and I realize
most people (including myself) don't want to do this, doing what gets
called a "nuke & pave," where a completely clean reinstall of the
operating system is done, any programs typically used reinstalled, and
user data transferred back results in a machine that is literally, "as good as new."
--

Brian -Windows 10, 64-Bit, Version 21H1, Build 19043

Yep. Discipline. Accountability. Joy. Fun. Responsibility.

That's what life is about. And in that order.

~ Liza Minnelli


Re: Adding more add-ons to the core

Sarah k Alawami
 

Mine is 4 years old, 8 cores and running Windows 10 21H1 (64-bit) build 19043.1110. It’s a grate machine except it is slow when I run stuff that takes up 100 percent of my first core.

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Arlene
Sent: Monday, July 19, 2021 3:18 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Adding more add-ons to the core

 

Hi Sarah, what version of windows are you using? If its ten. That’s bad.  These windows computers are cheaply made so you’d upgrade to the next version of windows.  I had an Acer for windows 7 box for 7 almost 8 years.  It died and I had to get a windows ten witch I now have.  I’ve had this computer for over 2 years and its starting to slow down. 

 

Sent from Mail for Windows 10

 

From: Sarah k Alawami
Sent: July 19, 2021 2:57 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Adding more add-ons to the core

 

OH yeah. I agree. I'm not really good with this software stuff but I'm already saving up for a new system as mine is starting to die, and that one should be able to support windows what ever by then and nvda what ever by then.

Blessings and happy Monday

On 19 Jul 2021, at 12:44, Brian Vogel wrote:

If you are a computer user it is incumbent on you to read the proverbial writing on the wall, and as it changes, and proceed accordingly.  You ignore it at your own peril.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 

 


Re: Adding more add-ons to the core

 

On Tue, Jul 20, 2021 at 11:49 AM, Curtis Delzer wrote:
and, wasn't it Bill Gates who said that "640K should be good enough for anybody?"
-
I believe it was, and at the time, it was also true.  Yet another demonstration of:  Nothing is so constant as change, and nowhere is change so constant and rapid as in the world of computing and electronics.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Re: Adding more add-ons to the core

Curtis Delzer
 

and, wasn't it Bill Gates who said that "640K should be good enough for anybody?"

Curtis Delzer
HS
K 6 V F O
Rialto, CA

curtis@...

On 7/19/2021 3:29 PM, Brian Vogel wrote:
On Mon, Jul 19, 2021 at 06:18 PM, Arlene wrote:
I’ve had this computer for over 2 years and its starting to slow down.
-
And?  This is:
1.  Expected, at least to some extent, as any machine becomes more used and, often, more stressed with new software.
2.  Is directly dependent on the hardware, operating system(s), and software.
I'm not saying you did this, but is an example of why a statement like yours really doesn't mean much without context, but if you buy a $200 machine with an Atom or Celeron class processor, it's actually at its maximum load in the Windows 10 era doing very, very little indeed.  It will slow down very quickly.
It's all about demands and capacities.  The higher your demands, the greater the capacities of the hardware needs to be.  And no $400 computer will come close to the performance, or longevity, of an $800 to $1000 machine.  While there's not a perfect relationship between higher dollar (or insert your unit of currency here) and higher performance, there is a direct one.  And having processing power "breathing room" as well as sufficient RAM are both really critical to minimizing the amount of slowing down as time goes on.
The operating system is irrelevant.  The technical specs of your hardware are.  Windows 10 can, and does, run beautifully on a great deal of late Windows 7 era hardware that was higher end when produced.  And it, conversely, runs poorly on hardware that "meets the minimum specifications" and not much more.
And even the very best, and most powerful, hardware will slow down with age, and that's mostly because of the "detritus of use" building up on the operating system side of things.  Most often, and I realize most people (including myself) don't want to do this, doing what gets called a "nuke & pave," where a completely clean reinstall of the operating system is done, any programs typically used reinstalled, and user data transferred back results in a machine that is literally, "as good as new."
--
Brian -Windows 10, 64-Bit, Version 21H1, Build 19043
Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.
That's what life is about.  And in that order.
        ~ Liza Minnelli


List for add-on developers?

Janet Brandly
 

Thank you for the info on resources for add-on developers. I will pass it on. If there are significant developments, I’ll share them here.

 

Janet B


Re: NVDA volume not adjustable in windows volume control

Gene
 

Without having the technical knowledge to  do more than speculate, this may be a minor corruption in the registry.  As a practical matter, does this matter?  NVDA has its own volume setting found by opening the dialog for the synthesizer you are using, JAWS key, control v, and tabbing through the fields.  A volume control will be found for the synthesizer you are using.  It will say volume and that’s it but it is actually adjusting that specific synthesizer as used by NVDA and appears completely independent of the volume control adjustment.
in NVDA.  Do you have such a setting and what does it do?  Will it meet your needs?
 
Gene

-----Original Message-----
Sent: Tuesday, July 20, 2021 8:52 AM
Subject: Re: [nvda] NVDA volume not adjustable in windows volume control
 

Hello David. I am using the Windows OneCore voices.

I’ve even tried the eSpeak just to see if there is a difference. Same thing happens.

 

 

Casey Mathews

WebFriendlyHelp.com: Makin’ your tech life easy!

 

 

 

From: David Goldfield
Sent: Monday, July 19, 2021 4:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA volume not adjustable in windows volume control

 

Casey, what synthesizer are you using with NVDA?

 

David Goldfield,

Blindness Assistive Technology Specialist

JAWS Certified, 2019

Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.

Email: tech-vi+subscribe@groups.io

 

www.DavidGoldfield.org

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Casey Mathews
Sent: Monday, July 19, 2021 9:50 AM
To: nvda.groups.io <nvda@nvda.groups.io>
Subject: [nvda] NVDA volume not adjustable in windows volume control

 

Hey all.

Right now in the volume control if I have NVDA set to sound mapper or headphones I am unable to adjust the volume in the volume control. When I do the volume for NVDA jumps back to 27%. This is 3% less than my normal audio in case that helps.

If I switch NVDA output to speakers I can then adjust the volume control.

I have disabled any volume add-ons and made sure that audio ducking is off.

I can adjust the volume in NVDA speech controls with no problem.

I am running NVDA 2021.1

Windows 10 21H1 (64-bit) build 19043.1110

 

 

Casey Mathews

WebFriendlyHelp.com: Makin’ your tech life easy!

 

 

 

 


Re: NVDA volume not adjustable in windows volume control

 

Hello David. I am using the Windows OneCore voices.

I’ve even tried the eSpeak just to see if there is a difference. Same thing happens.

 

 

Casey Mathews

WebFriendlyHelp.com: Makin’ your tech life easy!

 

 

 

From: David Goldfield
Sent: Monday, July 19, 2021 4:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA volume not adjustable in windows volume control

 

Casey, what synthesizer are you using with NVDA?

 

David Goldfield,

Blindness Assistive Technology Specialist

JAWS Certified, 2019

Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.

Email: tech-vi+subscribe@groups.io

 

www.DavidGoldfield.org

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Casey Mathews
Sent: Monday, July 19, 2021 9:50 AM
To: nvda.groups.io <nvda@nvda.groups.io>
Subject: [nvda] NVDA volume not adjustable in windows volume control

 

Hey all.

Right now in the volume control if I have NVDA set to sound mapper or headphones I am unable to adjust the volume in the volume control. When I do the volume for NVDA jumps back to 27%. This is 3% less than my normal audio in case that helps.

If I switch NVDA output to speakers I can then adjust the volume control.

I have disabled any volume add-ons and made sure that audio ducking is off.

I can adjust the volume in NVDA speech controls with no problem.

I am running NVDA 2021.1

Windows 10 21H1 (64-bit) build 19043.1110

 

 

Casey Mathews

WebFriendlyHelp.com: Makin’ your tech life easy!

 

 

 

 


Re: Compatibility of EnhancedPhoneticReading AddOn?

David Goldfield
 

Rui,

I, too, would sincerely like to thank you for taking the time to update this addon. While there are ways of quickly obtaining the phonetic equivalent of a character using the number pad this automatic feature is a capability that I’ve grown accustomed to with JAWS and is one that I’ve always wanted to see in NVDA. Having this, while a small change to some, makes using NVDA even more enjoyable for me. Thank you.

 

 

David Goldfield,

Blindness Assistive Technology Specialist

JAWS Certified, 2019

Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.

Email: tech-vi+subscribe@groups.io

 

www.DavidGoldfield.org

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Sunday, July 18, 2021 6:26 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Compatibility of Phoenetic character AddOn?

 

On Sun, Jul 18, 2021 at 06:23 PM, Rui Fontes wrote:

https://www.dropbox.com/s/q75mnyttr34zjpm/EnhancedPhoneticReading_0.5a2_Gen.nvda-addon?dl=1

-
Rui, thanks much for the updated link and for doing the mod.  Let's hope the original gets an "official update" from its developer.
 
@britechguy
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 

14741 - 14760 of 101101