Configuration Profiles and Triggers


 

In playing around with these features, I notice that there are three options related to when a configuration profile would be invoked:

Manual, Current Application (with that application named in parentheses after), and Say All.

I understand that the Manual invocation is just that.  There is no automatic triggering of that configuration profile and you have to ask for it.  I also understand that the Current Application option will create an automatic trigger such that when NVDA detects that the application has focus, that configuration profile will be used.

It's Say All that has me slightly confused, and it's about scope.  Is the Say All choice global, in that regardless of what application you may be in and what profile may be active, that will be overridden by what you set up for Say All?  Or is the Say All choice scoped underneath an existing configuration profile so that, say you have one for the Chrome browser and are in Chrome, would the Say All override in whatever way you have it configured already for Chrome, but not for anything else?
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

[Regarding the Supreme Court refusing to hear the case brought by Texas to overturn the votes certified by 4 states:Pleased with the SCOTUS ruling, but also immediately slightly terrified of where this crazy train goes next.  We should know by now there’s a bottomless supply of crazy.

        ~ Brendan Buck, former adviser to Speakers of the House Paul Ryan and John Boehner 

 

Join nvda@nvda.groups.io to automatically receive all group messages.