Date   
NVDA sound settings.

DaVid
 

Hi there.

We can set the sound device output for the synthetizers. But this
doesn't affect the general NVDA's sounds.E.G. tones, start NVDA
sound,ETC.
I usually use two audio cards, and sometimes I need NVDA on another
card. Its easy when I use DAWs like reaper, but difficult on less
specialized software.E.G. browsers.
Sometimes I want to play E.G. videos on youtube. Then I want to send
the signal via my dedicated apogee or roland cards, to listen them
from my studio monitors.
Firefox hasn't the option to change the sound output, so I need to
change it from the windows system settings and then, change the NVDA's
synthesizer output.
But since it doesn't affect the general sounds, is very annoying if
NVDA plays a sound; worse with my monitors at high volume.
So the sound output option should be moved to general settings I think.

I decided to comment here vefore open an issue. Its easy to solve, I think.
I have other issues when I use two or more cards, but I can live with
them. Those issues are present on another screen readers also.

Regards,
DaVid.

Re: Start tones on latest threshold but not staging

Brian's Mail list account
 

No its not the add ons, there are no rising tones on start up on the basic threshold build.
Another odd thing is an error even when add onse are supposed not to be loaded because it spots the name mismatch of pico even though its not actually supposed to load any add ons.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>
Sent: Thursday, July 18, 2019 11:10 AM
Subject: [nvda-devel] Start tones on latest threshold but not staging


I've just noticed that after downloading these two snaps the non staging one starts with no sound. I will have to turn off addons to see if that is the same. Most odd.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Start tones on latest threshold but not staging

Brian's Mail list account
 

I've just noticed that after downloading these two snaps the non staging one starts with no sound. I will have to turn off addons to see if that is the same. Most odd.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Trouble getting UIA Patterns

Karl-Otto Rosenqvist
 

Hi!
I've had a look in init.py for the UIA class and found an implementation for the UIASelectionPattern so I stole that and tried to get it working in an app module I'm working on. It's the grid I've written about earlier.

The problem is that I can't get hold of neither the selection pattern nor the table pattern even though NVDA + F! shows that the following patterns are availible.

UIA patterns available: LegacyIAccessiblePattern, GridPattern, ScrollPattern, SelectionPattern, TablePattern

role: ROLE_DATAGRID
states: STATE_FOCUSABLE, STATE_FOCUSED

Are the below functions dependant on something that's not implemented in NVDA or are there something I'm missing?


def _get_UIASelectionPattern(self):
try:
punk = self.GetCurrentPattern(UIAHandler.UIA_SelectionPatternId)
if punk:
self.UIASelectionPattern = punk.QueryInterface(UIAHandler.IUIAutomationSelectionPattern)
else:
self.UIASelectionPattern = None

return self.UIASelectionPattern
except:
log.debugWarning("No Selection Pattern")
return None

def _get_UIATablePattern(self):
try:
punk = self.GetCurrentPattern(UIAHandler.UIA_TablePatternId)
if punk:
self.UIATablePattern = punk.QueryInterface(UIAHandler.IUIAutomationTablePattern)
else:
self.UIATablePattern = None

return self.UIATablePattern
except:
log.debugWarning("No Table Pattern")
return None


Kind regards

Karl-Otto

--
Karl-Otto Rosenqvist
Mawingu
Orgnr: 750804-3937
0701- 75 98 56
karl-otto@...
https://mawingu.se

FW: [nvda] Braille and wx events

 

Hi,
I think we may need to advertise this list more given increasing frequency of dev questions sent to users list.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Vincent Le Goff
Sent: Tuesday, July 16, 2019 1:07 PM
To: nvda@nvda.groups.io
Subject: [nvda] Braille and wx events

Hi everyone,


Playing around with wxPython, I was wondering what the heck the Braille cursor routine do when clicked. It seems using them does not generate a click event that wxPython can intercept. Or a key event (some will interpret the Braille cursor keys as a series of left and right to go to the specified point, if possible). I've tried different mouse cursor event but nothing works (except when I use NVDA + pavnum-MouseLeft and pavnum-MouseLeft, which does generate these events).


Just curious how that's implemented. I use Braille routing on a daily basis, though usually in editors. Could someone tell me why these wx events are not generated when I click on my cursor routing keys? And if there are events I can link to (or, if not, why?).


Thanks!


Vincent

Re: load Symbol Pronunciations from file in add-on

Noelia Ruiz
 

Thanks, though this method is private, preceded by an underscore. I
will look at this. My idea was to use emojis or literal expressions as
symbols in emoticons add-on, which supports dictionaries associated to
profiles. I think this is better than speech dictionaries, since, when
using speech dictionaries with switching languages enabled, the
pronounciation is weird.
Hope dictionaries and symbols can be attached to profiles in NVDA (I
know there is at least an issue for this).

Cheers


2019-07-15 7:27 GMT+02:00, Leonard de Ruijter <leonard@...>:

Hello,


It really depends on what you're trying to do, but I think the best way
would probably be to call
characterProcessing._getSpeechSymbolsForLocale, and not to fiddle with
the symbols.dic file directly, unless you really need to.


Regards,

Leonard

Op 15-7-2019 om 04:25 schreef Noelia Ruiz:
Hi, I tried to do this, but since symbols come from different sources and
after looking characterProcessing.py, I didnt find a clean way to do this.
If someone can help I will be grateful too.
We use speech dictionaries in Emoticon add-on instead of symbols, in case
it is useful for you. The repo is at github.com bar nvdaes bar emoticons,
and it is available on the add-ons website.
Cheers


Enviado desde mi iPhone

El 14 jul 2019, a las 13:45, Jawhien <jawhien@...> escribió:

Hello.

Please tell me how to load the symbols.dic file from add-on?

I'm probably asking a simple thing, but I'm just learning python. Thank
you.




Re: load Symbol Pronunciations from file in add-on

 

Hello,


It really depends on what you're trying to do, but I think the best way would probably be to call characterProcessing._getSpeechSymbolsForLocale, and not to fiddle with the symbols.dic file directly, unless you really need to.


Regards,

Leonard

Op 15-7-2019 om 04:25 schreef Noelia Ruiz:

Hi, I tried to do this, but since symbols come from different sources and after looking characterProcessing.py, I didnt find a clean way to do this. If someone can help I will be grateful too.
We use speech dictionaries in Emoticon add-on instead of symbols, in case it is useful for you. The repo is at github.com bar nvdaes bar emoticons, and it is available on the add-ons website.
Cheers


Enviado desde mi iPhone

El 14 jul 2019, a las 13:45, Jawhien <jawhien@...> escribió:

Hello.

Please tell me how to load the symbols.dic file from add-on?

I'm probably asking a simple thing, but I'm just learning python. Thank you.





Re: load Symbol Pronunciations from file in add-on

Noelia Ruiz
 

Hi, I tried to do this, but since symbols come from different sources and after looking characterProcessing.py, I didnt find a clean way to do this. If someone can help I will be grateful too.
We use speech dictionaries in Emoticon add-on instead of symbols, in case it is useful for you. The repo is at github.com bar nvdaes bar emoticons, and it is available on the add-ons website.
Cheers


Enviado desde mi iPhone

El 14 jul 2019, a las 13:45, Jawhien <jawhien@...> escribió:

Hello.

Please tell me how to load the symbols.dic file from add-on?

I'm probably asking a simple thing, but I'm just learning python. Thank you.


load Symbol Pronunciations from file in add-on

Jawhien
 

Hello.

Please tell me how to load the symbols.dic file from add-on?

I'm probably asking a simple thing, but I'm just learning python. Thank you.

Re: NVDA - Get the input with nvda shortcut keys

derek riemer
 

In your original message, x is a local variable, so if you assign something to it, it will automatically be destroyed when the function goes out of scope. If you don't know what I'm talking about, I'd advise doing some python tutorials first, because addon development requires at least an intermediate, and probably closer to advanced knowledge of python. If you can do what you want without modifying the screen reader, you'll want to do so, because addon writing is far from a trivial undertaking.

On Sat, Jul 13, 2019 at 10:50 PM Derek Riemer <driemer.riemer@...> wrote:
Please note that NVDA already supports strikethrough. You need to configure it through the document formatting settings, and it's off by default to keep users from being spammed by needless information.

On Tue, Jul 9, 2019 at 1:51 PM vimuths via Groups.Io <vimuths=yahoo.com@groups.io> wrote:
When we create a simple web page and read this line with NVDA shortcut key H it will be read as
"Flash Sale heading level three"

<h3 class="hp-mod-card-title">Flash Sale</h3>

But is there a way to assign this Flash Sale to a python variable?. Really sorry I'm bit new to this.

import globalPluginHandler
import ui

class GlobalPlugin(globalPluginHandler.GlobalPlugin):

        def script_sayHeader(self, gesture):
                x = "Header 123"
                ui.message(x + 'is a nice header')

        __gestures={
                "kb:h":"sayHeader"
        }

This is the code for a global plugin I created and I need to add a current header or shortcut key value to this x. This is a sample code and what I intend to do is a bit complicated.



--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com






--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com




Re: NVDA - Get the input with nvda shortcut keys

derek riemer
 

Please note that NVDA already supports strikethrough. You need to configure it through the document formatting settings, and it's off by default to keep users from being spammed by needless information.

On Tue, Jul 9, 2019 at 1:51 PM vimuths via Groups.Io <vimuths=yahoo.com@groups.io> wrote:
When we create a simple web page and read this line with NVDA shortcut key H it will be read as
"Flash Sale heading level three"

<h3 class="hp-mod-card-title">Flash Sale</h3>

But is there a way to assign this Flash Sale to a python variable?. Really sorry I'm bit new to this.

import globalPluginHandler
import ui

class GlobalPlugin(globalPluginHandler.GlobalPlugin):

        def script_sayHeader(self, gesture):
                x = "Header 123"
                ui.message(x + 'is a nice header')

        __gestures={
                "kb:h":"sayHeader"
        }

This is the code for a global plugin I created and I need to add a current header or shortcut key value to this x. This is a sample code and what I intend to do is a bit complicated.



--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com




Re: Regression in UIA console support

Reef Turner
 

Thanks for bringing this up, there is work in progress to address this:

https://github.com/nvaccess/nvda/pull/9899

 

--

Reef Turner
Software Developer 

 

www.nvaccess.org

Facebook: https://www.facebook.com/NVAccess 
Twitter: @NVAccess 

 

From: francisco del roio
Sent: Thursday, 11 July 2019 12:53 PM
To: NVDA Development
Subject: [nvda-devel] Regression in UIA console support

 

Hello bill,

 

I found a regression in UIA console support, specifically under version

1903.

 

To reproduce it, do these steps:

 

1. Open any console.

2. Navigate to a git repository or prepare to use any command whose

output fills the entire screen.

3. Execute the command, for example "git log".

4. Maximize the console window.

5. Try to read with text review commands.

6. Do the same but without the window maximized (you'll need to restart

the console window).

 

Note that if you don't maximize, it works as expected.

 

Cheers,

--

Cuando tus fuerzas terminan, las de mi Dios comienzan.

 

 

 

Regression in UIA console support

francisco del roio
 

Hello bill,

I found a regression in UIA console support, specifically under version
1903.

To reproduce it, do these steps:

1. Open any console.
2. Navigate to a git repository or prepare to use any command whose
output fills the entire screen.
3. Execute the command, for example "git log".
4. Maximize the console window.
5. Try to read with text review commands.
6. Do the same but without the window maximized (you'll need to restart
the console window).

Note that if you don't maximize, it works as expected.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Is this a spelling error in the code?

Brian's Mail list account
 

While trying to find out about the now you see them,now you don't Espeak issue I came across this strange error reoccurring.


File "displayModel.pyc", line 554, in _getCaretOffset
File "displayModel.pyc", line 521, in _findCaretOffsetFromLocation
File "displayModel.pyc", line 325, in _getStoryOffsetLocations
File "baseObject.pyc", line 47, in __get__
File "baseObject.pyc", line 147, in _getPropertyViaCache
File "displayModel.pyc", line 285, in _get__storyFieldsAndRects
File "displayModel.pyc", line 183, in getWindowTextInRect
File "locationHelper.pyc", line 389, in __new__
ValueError: left=14021 is greather than right=-5824, which is not allowed

greather than

I think this was solved though by resetting to factory defaults and restarting with add ons off and then resetting the preferences.
Brian




bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Latest staging snap seems unable to see espeak variants in dialogue

Brian's Mail list account
 

Well I can't make it work on Windows 7 though the voices are in the archive in the v folder. Is this some strange path loss issue?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Re: FW: [nvda-addons] NVDA threshold branches and sapi5 Loquendo

 

Hello,


Posting issues like these on mailing lists easily make them go out of view.

I'd advice either you or the original reporter to file a github issue that contains steps to reproduce, possibly with a link to a demo version of the synth.


Regards,

Leonard

Op 8-7-2019 om 16:11 schreef Joseph Lee:

Hi,
Basically, Loquendo (now part of nuance Vocalizer Expressive) SAPI5 driver behaves oddly when trying to speak, according to the original poster (Adriano). I'll ask for a log.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Leonard de Ruijter
Sent: Monday, July 8, 2019 7:09 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] FW: [nvda-addons] NVDA threshold branches and sapi5 Loquendo

Joseph,

 Such a summary might make Could you summarize the use that's occurring?it more likely that someone will look into it.

Met vriendelijke groet, kind regards,

Leonard de Ruijter
Babbage Accessibility Engineer
Telefoon: 0165-536156
Emailadres: leonard@...
Skype: leonardbabbage
Website: www.babbage.com
Youtube
Facebook

Bezoekadres:
Bergrand 222
4707 AT Roosendaal
KVK: 20065000

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Joseph Lee
Sent: Monday, July 8, 2019 3:53 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] FW: [nvda-addons] NVDA threshold branches and sapi5 Loquendo

Hi,
Can we verify that speech refactor is to blame for the issues we're seeing here? Don't worry about Eloquence bit.
Cheers,
Jsoeph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Rui Fontes
Sent: Monday, July 8, 2019 6:46 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] NVDA threshold branches and sapi5 Loquendo

Sorry, but if Loquendo is a SAPI5 synth, it do not have any proprietary driver, since it will use the SAPI5 driver, and this one is made by NVDA...

So, it is NVDA that needs to correct the problem...

Best regards,

Rui Fontes
Tiflotecnia, Lda.


Às 14:35 de 08/07/2019, Tyler Spivey escreveu:
I think you completely misunderstood the original email.
1. The synthesizer worked correctly in a previous version of NVDA.
2. Without any changes to the synthesizer, just NVDA code, it no 
longer works correctly in the Python 3 snapshot version of NVDA.
 From this info, there is clearly a regression in NVDA.

My guess is speech refactor. What we don't know is whether this is 
triggering a synthesizer bug or an NVDA one.

On 7/8/2019 6:25 AM, Joseph Lee wrote:
Hi David and others,

Before it gets out of control, let me try to understand and clarify 
both sides:

Regarding Eloquence: the best people to talk to (for now) is Code 
Factory and Nuance staff, the folks behind the add-on and the company 
who has ultimate authority, respectively. Suffice to say that the 
add-on may have an initial difficulty with Python 3 version of NVDA 
based on source code for the add-on in front of me.

Regarding legacy code and unsupported speech synthesizers: as much as 
we wish to support legacy code as long as possible, there are times 
when it must be dropped (we’ve experienced this feeling in 2017 when 
we had a discussion about Windows XP support). One way to support 
legacy code, or at least some of it is collaborating and modernizing 
it, and I expect this will be done to the best of our abilities, 
especially for speech synthesizers.

Regarding Python 3 discussion: there is another thread that talks 
about Python 3 differences. As I clarified last week, folks are 
welcome to test Python 3 snapshots privately and do something about 
add-ons on their own; once Python 3 comes to NVDA alpha snapshots, 
that is the day when we will start contacting authors of popular 
add-ons for their stances on Python 3 transition (I myself will make 
a statement or two (or three) about add-ons under my belt then).

Cheers,

Joseph

*From:*nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io> *On Behalf Of *David Taylor via 
Groups.Io
*Sent:* Monday, July 8, 2019 2:20 AM
*To:* nvda-addons@nvda-addons.groups.io
*Subject:* Re: [nvda-addons] NVDA threshold branches and sapi5 
Loquendo

Oh well, if you want to stick to your principles and kill NVDA for 
most of us, don't say I didn't warn you. If you don't put users 
first, especially power users, the kind you need to work on addons 
and so on, NVDA will go back to where it was in 2010. I'm trying to 
save it for so many people here!

On 08/07/2019 10:13, zvonimir stanečić, 9a5dsz wrote:

    Sorry, but that what said Adriani is a reality.

    Loquendo is closed source, thus it is not open source and it is
    proprietary.

    Best

    Zvonimir

    *From:*nvda-addons@nvda-addons.groups.io
    <mailto:nvda-addons@nvda-addons.groups.io>
    <nvda-addons@nvda-addons.groups.io>
    <mailto:nvda-addons@nvda-addons.groups.io> *On Behalf Of *David
    Taylor via Groups.Io
    *Sent:* Monday, July 8, 2019 10:18 AM
    *To:* nvda-addons@nvda-addons.groups.io
    <mailto:nvda-addons@nvda-addons.groups.io>
    *Subject:* Re: [nvda-addons] NVDA threshold branches and sapi5 
Loquendo

    Look. NVDA is a free screen reader. The synth is the way it
    interacts with us, and therefore the most important factor aside
    from basic functionality. Devs need to remember that without 
users,
    the project fails. If the voices are ones that nobody can stand,
    they will start to pay for Jaws again. At the end of the day, 
while
    we appreciate addons and all that NVDA has done, you must 
remember,
    users come before development.  I really do not like this current
    attitude one little bit. Again, I say, while some change is
    inevitable, I am not dealing with headaches and the inability to 
do
    things efficiently any more just so that people can develop, end 
of
    story. I say once more, the day Eloquence without pauses dies,
    efficient  computing for the blind dies. Fortunately somebody off
    list helped me get an Eloquence that will carry on working and
    doesn't have the pauses, so I will be OK, but many will not.

    Cheers

    Dave

    On 08/07/2019 02:55, Adriani Botez wrote:

        hello,

        I am afraid but we cannot take into account every 
discontinued
        thing. Technology moves on and there will always be things 
which
        will not be updated as fast as NVDA itself. If that synths 
are
        so important to the community, then let‘s find the source 
code
        and change it accordingly. If this is not possible, then we 
will
        have to leave it behind unfortunately. That‘s how technology
        proggress simply works.

        Best

        Adriani

        Von meinem iPhone gesendet


        Am 08.07.2019 um 00:12 schrieb zvonimir stanečić, 9a5dsz
        <zvonimirek222@... <mailto:zvonimirek222@...>>:

            Hi Joseph,

            This thing cannot be solved by the synthesizer maker, as 
the
            synthesizer maker is merged with nuance, and due to this,
            loquendo synths are discontinued forever, and the synths 
are
            no longer sold.

            *From:*nvda-addons@nvda-addons.groups.io
            <mailto:nvda-addons@nvda-addons.groups.io>
            <nvda-addons@nvda-addons.groups.io
            <mailto:nvda-addons@nvda-addons.groups.io>> *On Behalf Of
            *Joseph Lee
            *Sent:* Sunday, July 7, 2019 11:58 PM
            *To:* nvda-addons@nvda-addons.groups.io
            <mailto:nvda-addons@nvda-addons.groups.io>
            *Subject:* Re: [nvda-addons] NVDA threshold branches and
            sapi5 Loquendo

            Hi,

            I advise contacting the synthesizer maker because they 
may
            have more info as to how to troubleshoot this. I’ll 
announce
            a more general directive regarding this kind of thing 
once
            NVDA’s master branch uses Python 3.

            Cheers,

            Joseph

            *From:*nvda-addons@nvda-addons.groups.io
            <mailto:nvda-addons@nvda-addons.groups.io>
            <nvda-addons@nvda-addons.groups.io
            <mailto:nvda-addons@nvda-addons.groups.io>> *On Behalf Of
            *Adriano Barbieri via Groups.Io
            *Sent:* Sunday, July 7, 2019 2:56 PM
            *To:* nvda-addons <nvda-addons@nvda-addons.groups.io
            <mailto:nvda-addons@nvda-addons.groups.io>>
            *Subject:* [nvda-addons] NVDA threshold branches and
sapi5
            Loquendo

            Hi to every one,

            I point out that iin this branch the sapi5 of the 
Loquendo
            do not work properly, the progress bars percentage are 
not
            read, the file name in the directories is not vocalized 
when
            positioned above it, it does not spell and with nvda + 
down
            arrow reads only one line at a time.
            The strange thing is that no error is generated, simply 
the
            ui.message () command in certain parts of the code is not
            vocalized by the speech synthesis, for example when 
reading
            the "Details" in Weather_Plus.
            I also tried adding wx.CallAfter () and wx.CallLater (), 
but
            it doesn't vocalize the string.
            I tried them all, I hope this is a temporary problem 
because
            the Loquendo sapi5 is widely used here in Italy.
            While with the same source code the speech synthesis 
works
            regularly with all previous versions of nvda, including 
the
            nvdapy37-20190228 version.

            Thanks

            Kind regards
            Adriano



















Re: FW: [nvda] Running NVDA as a virtualise app using App-v #winten1709

 

I've seen some attempts to package NVDA inside AppV, without much luck. May be we did it wrong, though.

As for audio ducking, I would say that it isn't at all important.


Regards,

Leonard

On 11-7-2019 04:46, Joseph Lee wrote:

Hi,

Any thoughts?

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Genevieve Nolasco
Sent: Wednesday, July 10, 2019 4:54 PM
To: nvda@nvda.groups.io
Subject: [nvda] Running NVDA as a virtualise app using App-v #winten1709

 

Hi guys, we use NVDA 2017.2 on Windows 7 and it is running as a virtualised app using App-v just fine. 

We are moving to use Windows 10 and so are transferring our apps across to the new OS.

We've had a few hurdles with using the newest version of NVDA 2019.1.1 as a virtualised app in win 10 though, but we've gotten over them so far. There's one that we are facing now that we are at a loss as to how to fix or get around.

We start it up and it seems to work fine, but when we open the log viewer we see at the bottom:
WARNING - audioDucking._setDeuckingState(10:22:18:661)
Unable to set ducking state:ERROR_ACCESS_DENIED.

It may well be some settings on our side that we are missing ie permission on a folder or something like that as the error suggests, but we're just now sure what impact this error has.

Is anyone able to tell us what this means and what it affects and potentially which location it might be trying to access and not allowed?

Also, can I confirm that we can use NVDA as a virtualized app? Maybe we just got lucky with the older version, but in reality NVDA should not be run as a virtual app.

Thanks in advance.

FW: [nvda] Running NVDA as a virtualise app using App-v #winten1709

 

Hi,

Any thoughts?

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Genevieve Nolasco
Sent: Wednesday, July 10, 2019 4:54 PM
To: nvda@nvda.groups.io
Subject: [nvda] Running NVDA as a virtualise app using App-v #winten1709

 

Hi guys, we use NVDA 2017.2 on Windows 7 and it is running as a virtualised app using App-v just fine. 

We are moving to use Windows 10 and so are transferring our apps across to the new OS.

We've had a few hurdles with using the newest version of NVDA 2019.1.1 as a virtualised app in win 10 though, but we've gotten over them so far. There's one that we are facing now that we are at a loss as to how to fix or get around.

We start it up and it seems to work fine, but when we open the log viewer we see at the bottom:
WARNING - audioDucking._setDeuckingState(10:22:18:661)
Unable to set ducking state:ERROR_ACCESS_DENIED.

It may well be some settings on our side that we are missing ie permission on a folder or something like that as the error suggests, but we're just now sure what impact this error has.

Is anyone able to tell us what this means and what it affects and potentially which location it might be trying to access and not allowed?

Also, can I confirm that we can use NVDA as a virtualized app? Maybe we just got lucky with the older version, but in reality NVDA should not be run as a virtual app.

Thanks in advance.

Re: NVDA - Get the input with nvda shortcut keys

James Scholes
 

There is a lot of information on the web about userscripts and browser extensions, including tutorials. You will need to know JavaScript and HTML, and potentially will also need to be familiar with ARIA concepts.

Regards,

James Scholes

On 10/07/2019 at 12:43 pm, vimuths via Groups.Io wrote:
I'm not familier with the term user scripts. Is there any tutorials?

Re: NVDA - Get the input with nvda shortcut keys

vimuths@...
 

I'm not familier with the term user scripts. Is there any tutorials?