Date   
Strange issue with NVDA and queueHandler.eventQueue?

DaVid
 

Hi there.
Today my copy of NVDA was blocked. I was using chrome at the time.
When I read the log, the function that froze NVDA was "queue.empty()"
But "queue.empty" is used to check if the queue has pending tasks or not. So, this function shoulndn't block anything.
I was unable to restart NVDA. Then I slept my laptop and started it again, NVDA didn't respond but in this case I could restart NVDA.
This is the log:

WARNING - watchdog._watcher (18:10:17.574) - watchdog (3208):
Core frozen in stack:
  File "nvda.pyw", line 215, in <module>
  File "core.pyc", line 545, in main
  File "wx\core.pyc", line 2134, in MainLoop
  File "gui\__init__.pyc", line 1030, in Notify
  File "core.pyc", line 515, in run
  File "queueHandler.pyc", line 83, in pumpAll
  File "queueHandler.pyc", line 46, in flushQueue
  File "queue.pyc", line 107, in empty

Regards,
David CM
Ingeniero en computación (ITCR)
Experto certificado en NVDA.
correo: dhf360@...

Encuentra mis proyectos libres en github.
y las publicaciones en mi canal de youtube.

Suscríbite y aprende en mis grupos de correo y facebook:
Programación accesible:
Envía un correo de suscripción a la dirección: programacionaccesible+subscribe@...
O participa en Programación accesible en Facebook.

tiflotronica: Si te gusta la electricidad y los chips ¡Aprende y aporta sobre este tema tan apasionante!
Envía un correo de suscripción a la dirección: tiflotronica+subscribe@...
Si te gusta la producción o ejecución de instrumentos musicales, participa en Músicos ciegos y de baja visión en facebook.
También puedes hacer tus consultas sobre tu lector de pantallas favorito en la comunidad de NVDA en español (facebook)

Dual Voice add-on: is anyone willing to make it NVDA 2019.3 ready?

 

Hi all,

 

As noted in the following GitHub issue:

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

 

Dual Voice add-on isn’t NVDA 2019.3 ready, and attempts to contact the author isn’t working. So may I suggest someone taking a look at this add-on and see what can be done? The add-on can be found at:

https://addons.nvda-project.org/addons/dualvoice.en.html

 

Cheers,

Joseph

Re: [nvda] NVDA 2019.3 Beta 3 now available

Rui Fontes
 

Hello!


The problem is not how to know what character is...

The problem is that this NVDA version causes a serious problem and we are not yet absolutly sure which add-on is the culpry... and why...


For me, it is a show stopper problem...


Rui Fontes

NVDA portuguese team


Às 09:05 de 30/01/2020, hurrikennyandopo ... escreveu:

Hi


are you talking about the add on that after a second or 2 would say the letter  it was on like A  for alfa B for bravo etc.


I just can not think what that add on name was called.


are you aware also you can find out what the letter is on the numeric keypad if using the review cursor


Hitting the number 2 of the numeric keypad 2 times would say it like that or 5 on the numeric key pad would do the word if hit 3 times..


Gene nz


On 30/01/2020 9:47 pm, Ralf Kefferpuetz wrote:

Hi Quentin,

Reading by character stopped for me in this version as well as in any alpha version newer than 28th Jan.

 

Cheers,

Ralf

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Donnerstag, 30. Januar 2020 01:49
To: nvda@nvda.groups.io
Subject: [nvda] NVDA 2019.3 Beta 3 now available

 

Hi everyone,

 

As you are all quick off the mark, this isn't completely new news, but confirming that yes, NVDA 2019.3 beta 3 is now available from: https://www.nvaccess.org/post/nvda-2019-3beta3-now-available-for-testing/ 

 

This is slight progression from the previous beta so you shouldn't notice too many big changes - of course as always happens, as we move closer to the final release, we don't put as many big new features in, but rather try to ensure that everything is stable and fix bugs people have reported in previous betas.

 

If you do encounter any issues, please do report them: https://github.com/nvaccess/nvda/issues  If you could also clarify whether they are new issues or existing issues (which hadn't previously been reported) that would be really helpful - both are important to know about, but being able to pinpoint when something started being an issue helps narrow down where to look for a fix.

 

All things going well, this will be the last beta before the release candidate, which will be just before the final stable release.

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 

Re: Object properties in speech functions

Reef Turner
 

I think this would be quite hard to achieve currently. Note that we have previously recommended this as a project for Google Summer of Code: https://github.com/nvaccess/nvda/wiki/GSOC-2019-Ideas-List#customize-order-and-inclusion-of-object-and-formatting-information-to-speech-and-braille.

My thoughts on a pathway towards this, is gradually convert all items in a speech sequence to some kind of speech command. Wrapping string items with a class that includes some metadata about it's origin. Eventually disallowing str objects in the speech sequence. Tagging speech that is essentially "NVDA UI" (eg "focus mode", or "selected" in "x selected"), as well tagging "name", "role", "value", "description" text could allow for some interesting innovation in how speech is presented.

I don't have a timeline on this. Note, this would be a compatibility breaking change.

Re: Object properties in speech functions

Alberto Buffolino
 

James Scholes, il 28/01/2020 21.31, ha scritto:
But the comment before the function in question seems to indicate that this part of the code is crying out for a refactor anyway:
Alberto:
true. As many other functions of speech module.
So... I'll see in future :)
Thanks James for replies.
Alberto

Re: Object properties in speech functions

James Scholes
 

Makes sense, and from a glance over the code, your assertion is correct. You would need to monkey-patch that function, presumably, to achieve what you're after. But the comment before the function in question seems to indicate that this part of the code is crying out for a refactor anyway:

# C901 'getPropertiesSpeech' is too complex
# Note: when working on getPropertiesSpeech, look for opportunities to simplify
# and move logic out into smaller helper functions.

Regards,

James Scholes

On 28/01/2020 at 2:21 pm, Alberto Buffolino wrote:
James Scholes, il 28/01/2020 21.01, ha scritto:
I'm not sure what you're asking.  Could you expand on your use case, and why you believe it is currently not feasible?
Alberto:
Hi James,
some users have asked me to provide a way to customize NVDA when it speaks objects, so to sort or hide some information. For example, to have "checked Save configuration on exit Checkbox", instead of "Save configuration on exit checkbox checked".
I was asking for a confirmation about my comprehension of object information processing. If it is as I think, I can do nothing with a add-on that simply changes order of information in properties/speechSequence before/after getPropertiesSpeech execution.
Ok, I'm not sure it's more clear now... 😅
Alberto

Re: Object properties in speech functions

Alberto Buffolino
 

James Scholes, il 28/01/2020 21.01, ha scritto:
I'm not sure what you're asking.  Could you expand on your use case, and why you believe it is currently not feasible?
Alberto:
Hi James,
some users have asked me to provide a way to customize NVDA when it speaks objects, so to sort or hide some information. For example, to have "checked Save configuration on exit Checkbox", instead of "Save configuration on exit checkbox checked".
I was asking for a confirmation about my comprehension of object information processing. If it is as I think, I can do nothing with a add-on that simply changes order of information in properties/speechSequence before/after getPropertiesSpeech execution.
Ok, I'm not sure it's more clear now... 😅
Alberto

Re: Object properties in speech functions

James Scholes
 

I'm not sure what you're asking. Could you expand on your use case, and why you believe it is currently not feasible?

Regards,

James Scholes

On 28/01/2020 at 12:43 pm, Alberto Buffolino wrote:
Hi all,
I'm investigating about NVDA verbosity/object information order, for a possible add-on or pr.
If I understand correctly, at this time the more important point concerns speech.getPropertiesSpeech, that provides the main speech sequence according to a passed dictionary of properties to process (name, role, etc). But, I suppose, there is no guarantee that properties passed will have a value in speech sequence, so no mapping property->value is possible (from an add-on perspective).
Right?
Thanks for replies.
Alberto

Object properties in speech functions

Alberto Buffolino
 

Hi all,
I'm investigating about NVDA verbosity/object information order, for a possible add-on or pr.
If I understand correctly, at this time the more important point concerns speech.getPropertiesSpeech, that provides the main speech sequence according to a passed dictionary of properties to process (name, role, etc). But, I suppose, there is no guarantee that properties passed will have a value in speech sequence, so no mapping property->value is possible (from an add-on perspective).
Right?
Thanks for replies.
Alberto

Re: Possible regression in NVDA 2019.3beta2 with screen curtain

Noelia Ruiz
 

In case, I will create a PR now that I have time. If not needed, we
can close it later.


2020-01-24 9:01 GMT+01:00, Noelia Ruiz via Groups.Io
<nrm1977=gmail.com@groups.io>:

I have created issue 10717 and branch fixScreenCurtain at
https://github.com/nvdaes/nvda

Should I create a PR against beta, or should be wait so that
@leonardder fix this?
Thanks.

2020-01-24 7:27 GMT+01:00, Noelia Ruiz via Groups.Io
<nrm1977=gmail.com@groups.io>:
Thanks Cyrille. I confirm you are right. I have fixed this locally by
removing a clause in globalCommands._enableScriptCurtain introduced in
this commit. Seems that when pressing twice the keystroke, one of them
is enabled temporarily and when the dialog confirmation is not shown,
the script is executed inmediately, so with this if... clause pressing
twice screen curtain is temporarily enabled but then disabled, not
enabled permanently. With my change the sound is heart twice when
performing a permanent enable, though for me this is not a problem

def _enableScreenCurtain(doEnable: bool = True):
self._waitingOnScreenCurtainWarningDialog = None
if not doEnable:
return # exit early with no ui.message because the user has
decided to abort.

tempEnable = GlobalCommands._tempEnableScreenCurtain
# Translators: Reported when the screen curtain is enabled.
enableMessage = _("Screen curtain enabled")
if tempEnable:
# Translators: Reported when the screen curtain is temporarily
enabled.
enableMessage = _("Temporary Screen curtain, enabled until next
restart")
- if not alreadyRunning:
try:
vision.handler.initializeProvider(
screenCurtainProviderInfo,
temporary=tempEnable,
)
except Exception:
log.error("Screen curtain initialization error", exc_info=True)
# Translators: Reported when the screen curtain could not be
enabled.
enableMessage = _("Could not enable screen curtain")
finally:

2020-01-23 23:54 GMT+01:00, Cyrille via Groups.Io
<cyrille.bougot2=laposte.net@groups.io>:
Hello

I have made tries with the profile switch procedure by switching between
an
app with specific profile and an app without specific profile (general
configuration).
I have found that the commit that has introduced this regression is the
following:
commit f194afaec02a3465ceb769ee88543ea337c6eb9e
Author: Leonard de Ruijter <leonardder@...>
Date: Mon Jan 13 00:27:57 2020 +0100
Optionally play sounds when toggling screen curtain (#10611)
* Add scree curtain sounds, ensure that it only enables once
* Add Andre Louis as a contributor
* Use mono sounds instead
* Update user guide, review actions

Looking at the log, I can see that the __init__ method of the screen
curtain
provider is not called when I turn back to the app where I previously
had
activated it permanently. However I cannot figure very well why it is
not
called anymore looking at the diff of this commit.

@leonardder:
Do you have an idea?

Thanks.
Cheers,

Cyrille


-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Noelia
Ruiz
Envoyé : jeudi 23 janvier 2020 19:53
À : nvda-devel@groups.io
Objet : Re: [nvda-devel] Possible regression in NVDA 2019.3beta2 with
screen
curtain

Thanks Alberto.
If this is specific of beta2, maybe related to commit
cd5b11332cc1c4d0b5497cefc66fd30bc91fd987

@Cyrille, what do you think?
Cheers

2020-01-23 19:26 GMT+01:00, Alberto Buffolino <a.buffolino@...>:
Noelia Ruiz, il 23/01/2020 19.14, ha scritto:
- NVDA reports that screen curtain has been enabled (permanently),
but this is set to False in configuration and is not enabled when
NVDA is restarted.
Alberto:
I confirm, just tried. Even not restarting, changing to another
profile and then switching again to previous where screen curtain
should be enabled is sufficient to see the problem. Warning and sound
disabled.
Alberto













I don't think this error matters on beta 2

Brian's Mail list account
 

However in case it does it was created by accidentally hitting say all while in the radio buttons on Microsoft Security essentials in windows 7.
IO - inputCore.InputManager.executeGesture (11:23:22.141) - winInputHook (5028):
Input: kb(desktop):NVDA+downArrow
ERROR - scriptHandler.executeScript (11:23:22.161) - MainThread (3940):
error executing script: <bound method GlobalCommands.script_sayAll of <globalCommands.GlobalCommands object at 0x02FCE290>> with gesture 'NVDA+down arrow'
Traceback (most recent call last):
File "scriptHandler.pyc", line 205, in executeScript
File "globalCommands.pyc", line 1368, in script_sayAll
File "sayAllHandler.pyc", line 79, in readText
File "sayAllHandler.pyc", line 119, in nextLine
AttributeError: '_TextReader' object has no attribute 'reader'
ERROR - stderr (11:23:22.161) - MainThread (3940):
Exception ignored in:
ERROR - stderr (11:23:22.171) - MainThread (3940):
<function _TextReader.__del__ at 0x03E58858>
ERROR - stderr (11:23:22.171) - MainThread (3940):
Traceback (most recent call last):
ERROR - stderr (11:23:22.181) - MainThread (3940):
File "sayAllHandler.pyc", line 213, in __del__
ERROR - stderr (11:23:22.181) - MainThread (3940):
File "sayAllHandler.pyc", line 206, in stop
ERROR - stderr (11:23:22.181) - MainThread (3940):
AttributeError
ERROR - stderr (11:23:22.181) - MainThread (3940):
:
ERROR - stderr (11:23:22.181) - MainThread (3940):
'_TextReader' object has no attribute 'reader'
IO - inputCore.InputManager.executeGesture (11:23:34.103) - winInputHook (5028):
Input: kb(desktop):control+alt+r
IO - speech.speak (11:23:34.153) - MainThread (3940):
Speaking [LangChangeCommand ('en_GB'), 'Taskbar']
IO - speech.speak (11:23:34.313) - MainThread (3940):
Speaking [LangChangeCommand ('en_GB'), 'reboot nvda with log']

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: Possible regression in NVDA 2019.3beta2 with screen curtain

Noelia Ruiz
 

I have created issue 10717 and branch fixScreenCurtain at
https://github.com/nvdaes/nvda

Should I create a PR against beta, or should be wait so that
@leonardder fix this?
Thanks.

2020-01-24 7:27 GMT+01:00, Noelia Ruiz via Groups.Io
<nrm1977=gmail.com@groups.io>:

Thanks Cyrille. I confirm you are right. I have fixed this locally by
removing a clause in globalCommands._enableScriptCurtain introduced in
this commit. Seems that when pressing twice the keystroke, one of them
is enabled temporarily and when the dialog confirmation is not shown,
the script is executed inmediately, so with this if... clause pressing
twice screen curtain is temporarily enabled but then disabled, not
enabled permanently. With my change the sound is heart twice when
performing a permanent enable, though for me this is not a problem

def _enableScreenCurtain(doEnable: bool = True):
self._waitingOnScreenCurtainWarningDialog = None
if not doEnable:
return # exit early with no ui.message because the user has
decided to abort.

tempEnable = GlobalCommands._tempEnableScreenCurtain
# Translators: Reported when the screen curtain is enabled.
enableMessage = _("Screen curtain enabled")
if tempEnable:
# Translators: Reported when the screen curtain is temporarily
enabled.
enableMessage = _("Temporary Screen curtain, enabled until next
restart")
- if not alreadyRunning:
try:
vision.handler.initializeProvider(
screenCurtainProviderInfo,
temporary=tempEnable,
)
except Exception:
log.error("Screen curtain initialization error", exc_info=True)
# Translators: Reported when the screen curtain could not be enabled.
enableMessage = _("Could not enable screen curtain")
finally:

2020-01-23 23:54 GMT+01:00, Cyrille via Groups.Io
<cyrille.bougot2=laposte.net@groups.io>:
Hello

I have made tries with the profile switch procedure by switching between
an
app with specific profile and an app without specific profile (general
configuration).
I have found that the commit that has introduced this regression is the
following:
commit f194afaec02a3465ceb769ee88543ea337c6eb9e
Author: Leonard de Ruijter <leonardder@...>
Date: Mon Jan 13 00:27:57 2020 +0100
Optionally play sounds when toggling screen curtain (#10611)
* Add scree curtain sounds, ensure that it only enables once
* Add Andre Louis as a contributor
* Use mono sounds instead
* Update user guide, review actions

Looking at the log, I can see that the __init__ method of the screen
curtain
provider is not called when I turn back to the app where I previously had
activated it permanently. However I cannot figure very well why it is not
called anymore looking at the diff of this commit.

@leonardder:
Do you have an idea?

Thanks.
Cheers,

Cyrille


-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Noelia
Ruiz
Envoyé : jeudi 23 janvier 2020 19:53
À : nvda-devel@groups.io
Objet : Re: [nvda-devel] Possible regression in NVDA 2019.3beta2 with
screen
curtain

Thanks Alberto.
If this is specific of beta2, maybe related to commit
cd5b11332cc1c4d0b5497cefc66fd30bc91fd987

@Cyrille, what do you think?
Cheers

2020-01-23 19:26 GMT+01:00, Alberto Buffolino <a.buffolino@...>:
Noelia Ruiz, il 23/01/2020 19.14, ha scritto:
- NVDA reports that screen curtain has been enabled (permanently),
but this is set to False in configuration and is not enabled when
NVDA is restarted.
Alberto:
I confirm, just tried. Even not restarting, changing to another
profile and then switching again to previous where screen curtain
should be enabled is sufficient to see the problem. Warning and sound
disabled.
Alberto











Re: Possible regression in NVDA 2019.3beta2 with screen curtain

Noelia Ruiz
 

Thanks Cyrille. I confirm you are right. I have fixed this locally by
removing a clause in globalCommands._enableScriptCurtain introduced in
this commit. Seems that when pressing twice the keystroke, one of them
is enabled temporarily and when the dialog confirmation is not shown,
the script is executed inmediately, so with this if... clause pressing
twice screen curtain is temporarily enabled but then disabled, not
enabled permanently. With my change the sound is heart twice when
performing a permanent enable, though for me this is not a problem

def _enableScreenCurtain(doEnable: bool = True):
self._waitingOnScreenCurtainWarningDialog = None
if not doEnable:
return # exit early with no ui.message because the user has
decided to abort.

tempEnable = GlobalCommands._tempEnableScreenCurtain
# Translators: Reported when the screen curtain is enabled.
enableMessage = _("Screen curtain enabled")
if tempEnable:
# Translators: Reported when the screen curtain is temporarily enabled.
enableMessage = _("Temporary Screen curtain, enabled until next restart")
- if not alreadyRunning:
try:
vision.handler.initializeProvider(
screenCurtainProviderInfo,
temporary=tempEnable,
)
except Exception:
log.error("Screen curtain initialization error", exc_info=True)
# Translators: Reported when the screen curtain could not be enabled.
enableMessage = _("Could not enable screen curtain")
finally:

2020-01-23 23:54 GMT+01:00, Cyrille via Groups.Io
<cyrille.bougot2=laposte.net@groups.io>:

Hello

I have made tries with the profile switch procedure by switching between an
app with specific profile and an app without specific profile (general
configuration).
I have found that the commit that has introduced this regression is the
following:
commit f194afaec02a3465ceb769ee88543ea337c6eb9e
Author: Leonard de Ruijter <leonardder@...>
Date: Mon Jan 13 00:27:57 2020 +0100
Optionally play sounds when toggling screen curtain (#10611)
* Add scree curtain sounds, ensure that it only enables once
* Add Andre Louis as a contributor
* Use mono sounds instead
* Update user guide, review actions

Looking at the log, I can see that the __init__ method of the screen curtain
provider is not called when I turn back to the app where I previously had
activated it permanently. However I cannot figure very well why it is not
called anymore looking at the diff of this commit.

@leonardder:
Do you have an idea?

Thanks.
Cheers,

Cyrille


-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Noelia Ruiz
Envoyé : jeudi 23 janvier 2020 19:53
À : nvda-devel@groups.io
Objet : Re: [nvda-devel] Possible regression in NVDA 2019.3beta2 with screen
curtain

Thanks Alberto.
If this is specific of beta2, maybe related to commit
cd5b11332cc1c4d0b5497cefc66fd30bc91fd987

@Cyrille, what do you think?
Cheers

2020-01-23 19:26 GMT+01:00, Alberto Buffolino <a.buffolino@...>:
Noelia Ruiz, il 23/01/2020 19.14, ha scritto:
- NVDA reports that screen curtain has been enabled (permanently),
but this is set to False in configuration and is not enabled when
NVDA is restarted.
Alberto:
I confirm, just tried. Even not restarting, changing to another
profile and then switching again to previous where screen curtain
should be enabled is sufficient to see the problem. Warning and sound
disabled.
Alberto









Re: Possible regression in NVDA 2019.3beta2 with screen curtain

Cyrille
 

Hello

I have made tries with the profile switch procedure by switching between an app with specific profile and an app without specific profile (general configuration).
I have found that the commit that has introduced this regression is the following:
commit f194afaec02a3465ceb769ee88543ea337c6eb9e
Author: Leonard de Ruijter <leonardder@...>
Date: Mon Jan 13 00:27:57 2020 +0100
Optionally play sounds when toggling screen curtain (#10611)
* Add scree curtain sounds, ensure that it only enables once
* Add Andre Louis as a contributor
* Use mono sounds instead
* Update user guide, review actions

Looking at the log, I can see that the __init__ method of the screen curtain provider is not called when I turn back to the app where I previously had activated it permanently. However I cannot figure very well why it is not called anymore looking at the diff of this commit.

@leonardder:
Do you have an idea?

Thanks.
Cheers,

Cyrille

-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Noelia Ruiz
Envoyé : jeudi 23 janvier 2020 19:53
À : nvda-devel@groups.io
Objet : Re: [nvda-devel] Possible regression in NVDA 2019.3beta2 with screen curtain

Thanks Alberto.
If this is specific of beta2, maybe related to commit
cd5b11332cc1c4d0b5497cefc66fd30bc91fd987

@Cyrille, what do you think?
Cheers

2020-01-23 19:26 GMT+01:00, Alberto Buffolino <a.buffolino@...>:
Noelia Ruiz, il 23/01/2020 19.14, ha scritto:
- NVDA reports that screen curtain has been enabled (permanently),
but this is set to False in configuration and is not enabled when
NVDA is restarted.
Alberto:
I confirm, just tried. Even not restarting, changing to another
profile and then switching again to previous where screen curtain
should be enabled is sufficient to see the problem. Warning and sound disabled.
Alberto



Re: Possible regression in NVDA 2019.3beta2 with screen curtain

Noelia Ruiz
 

Thanks Alberto.
If this is specific of beta2, maybe related to commit
cd5b11332cc1c4d0b5497cefc66fd30bc91fd987

@Cyrille, what do you think?
Cheers

2020-01-23 19:26 GMT+01:00, Alberto Buffolino <a.buffolino@...>:

Noelia Ruiz, il 23/01/2020 19.14, ha scritto:
- NVDA reports that screen curtain has been enabled (permanently), but
this is set to False in configuration and is not enabled when NVDA is
restarted.
Alberto:
I confirm, just tried. Even not restarting, changing to another profile
and then switching again to previous where screen curtain should be
enabled is sufficient to see the problem. Warning and sound disabled.
Alberto



Re: Possible regression in NVDA 2019.3beta2 with screen curtain

Alberto Buffolino
 

Noelia Ruiz, il 23/01/2020 19.14, ha scritto:
- NVDA reports that screen curtain has been enabled (permanently), but
this is set to False in configuration and is not enabled when NVDA is
restarted.
Alberto:
I confirm, just tried. Even not restarting, changing to another profile and then switching again to previous where screen curtain should be enabled is sufficient to see the problem. Warning and sound disabled.
Alberto

Possible regression in NVDA 2019.3beta2 with screen curtain

Noelia Ruiz
 

Hello:

This has been reported by two users of NVDA in Spanish. One of them
has sent me the log in debug level and nvda.ini. Also, he has tested
this with add-ons disabled.

# Test environment

- Windows version 10.0.18363 workstation
- Language set to Windows (Spanish).


- Using braille and speech.

# STR:

- Press twice the keystroke to activate screen curtain.

# Actual

- NVDA reports that screen curtain has been enabled (permanently), but
this is set to False in configuration and is not enabled when NVDA is
restarted.

# Aditional context

- Screen curtain is properly enabled when using the Vision panel (NVDA's gui).
- The warning dialog of screen curtain is disabled.
- This issue is specific of NVDA 2019.3beta2, worked properly with beta1.

Thanks

Python3 standard library

Andy B.
 

Hi,

It has come to my attention from experience that the entire standard library for Python 3 is not included in NVDA. I am trying to continue with Developer toolkit, but missing packages in NVDA's version of Python 3.7.5 makes it impossible. At this point, I am missing xml.dom and all of its sub packages. I'm sure there's more, but this is what I noticed so far. NVDA should include the entire standard library instead of cutting it away to save space.


Re: update regarding addon workflow

Cyrille
 

Hello
@Joseph:
Thanks for clarification. And sorry not to have read carefully all e-mails.
@Beqa:
When you have created a personal repo for InstantTranslate, let me know so that I can make (again) a PR. Thanks.
Cheers,
Cyrille
----- Mail d'origine -----
De: Joseph Lee <joseph.lee22590@...>
À: nvda-devel@groups.io
Envoyé: Mon, 20 Jan 2020 17:09:26 +0100 (CET)
Objet: Re: [nvda-devel] update regarding addon workflow
Hi,
As I wrote a while ago (and affirmed by add-on release workflow proposed by Mesar and Reef), people should be working from their own personal repositories, not from nvdaaddonns organization version of the repo. The organization version is meant for exchanging localization and release data, not as the primary development repo. As such, I will not review any pull requests for nvdaaddons repo changes if the PR does not come from personal repos. This applies to not just Instant Translate, but also other ones where Bitbucket repo was used as primary development repository.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Cyrille via Groups.Io
Sent: Sunday, January 19, 2020 2:09 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] update regarding addon workflow
When we were using Bitbucket, Beqa used to integrate directly the Pullrequests in the NVDA addons organisation's repo.
He was expecting to have the same rights in GitHub nvdaaddons organization. So, unless I am mistaken, he does not have a personal repo for this add-on.
So my question was: who has the right to merge the following PR:
https://github.com/nvdaaddons/instantTranslate/pull/1
If Beqa does not have the right to do it, how does he validate it as the current maintener (and co-author) of this add-on?
@Beqa:
If you have any news on this, let me know.
Thanks.
Cheers,
Cyrille
-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Noelia Ruiz Envoyé : dimanche 19 janvier 2020 22:53 À : nvda-devel@groups.io Objet : Re: [nvda-devel] update regarding addon workflow
Hello, as a person who helped Mesar, I confirm that instantTranslate is available on GitHub nvdaaddons organization, as well as all maintained add-ons previously available on BitBucket. Not sure if Beqa has a personal repo for this add-on too or if pull requests have to be sent there befor, but maintained add-ons should be available on GitHub.Cheers
Enviado desde mi iPhone
> El 19 ene 2020, a las 22:21, Cyrille via Groups.Io <cyrille.bougot2@...> escribió:
>
> Hello
>
> Thanks for all work.
>
> What about add-ons that were using directly the Bitbucket repo as main repo?
> I am thingking about Instant Translate on which Beqa had the right to
> merge the pull requests?
> Are the right transferred on Github? Can Beqa merge now my PR on this
> add-on?
> If no, should a separate fork become the main add-on's repo?
>
> Thanks.
> Regards,
>
> Cyrille
>
>
> -----Message d'origine-----
> De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Mesar
> Hameed Envoyé : dimanche 19 janvier 2020 20:35 À :
> nvda-devel@groups.io; nvda-addons@nvda-addons.groups.io Objet :
> [nvda-devel] update regarding addon workflow
>
> Dear Friends,
>
> After my original proposal, and Reef's proposal, and the various
> feedback we have had on both mailing lists, we will review everything
> and will come up with a unified solution.
>
> Considering the closeness of 2019.3, and the various work that addon
> authors have to do with regard to python 2 to 3 migration, additional
> metadata etc, we ask you to please continue working as before the
> migration from bitbucket, with the exception that all the repos are now on github.
>
> If you can get into the habbit of topic branches, pull requests, and
> reviewing each others work that would be great.
>
> If you took the time to read the proposed workflows, thank you, we
> will get back to you.
>
> Thank you for reading.
> Mesar
>
>
>
>
>
>
>

Re: update regarding addon workflow

 

Hi,
As I wrote a while ago (and affirmed by add-on release workflow proposed by Mesar and Reef), people should be working from their own personal repositories, not from nvdaaddonns organization version of the repo. The organization version is meant for exchanging localization and release data, not as the primary development repo. As such, I will not review any pull requests for nvdaaddons repo changes if the PR does not come from personal repos. This applies to not just Instant Translate, but also other ones where Bitbucket repo was used as primary development repository.
Cheers,
Joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Cyrille via Groups.Io
Sent: Sunday, January 19, 2020 2:09 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] update regarding addon workflow

When we were using Bitbucket, Beqa used to integrate directly the Pullrequests in the NVDA addons organisation's repo.
He was expecting to have the same rights in GitHub nvdaaddons organization. So, unless I am mistaken, he does not have a personal repo for this add-on.
So my question was: who has the right to merge the following PR:
https://github.com/nvdaaddons/instantTranslate/pull/1
If Beqa does not have the right to do it, how does he validate it as the current maintener (and co-author) of this add-on?

@Beqa:
If you have any news on this, let me know.

Thanks.
Cheers,

Cyrille

-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Noelia Ruiz Envoyé : dimanche 19 janvier 2020 22:53 À : nvda-devel@groups.io Objet : Re: [nvda-devel] update regarding addon workflow

Hello, as a person who helped Mesar, I confirm that instantTranslate is available on GitHub nvdaaddons organization, as well as all maintained add-ons previously available on BitBucket. Not sure if Beqa has a personal repo for this add-on too or if pull requests have to be sent there befor, but maintained add-ons should be available on GitHub.Cheers

Enviado desde mi iPhone

El 19 ene 2020, a las 22:21, Cyrille via Groups.Io <cyrille.bougot2=laposte.net@groups.io> escribió:

Hello

Thanks for all work.

What about add-ons that were using directly the Bitbucket repo as main repo?
I am thingking about Instant Translate on which Beqa had the right to
merge the pull requests?
Are the right transferred on Github? Can Beqa merge now my PR on this
add-on?
If no, should a separate fork become the main add-on's repo?

Thanks.
Regards,

Cyrille


-----Message d'origine-----
De : nvda-devel@groups.io <nvda-devel@groups.io> De la part de Mesar
Hameed Envoyé : dimanche 19 janvier 2020 20:35 À :
nvda-devel@groups.io; nvda-addons@nvda-addons.groups.io Objet :
[nvda-devel] update regarding addon workflow

Dear Friends,

After my original proposal, and Reef's proposal, and the various
feedback we have had on both mailing lists, we will review everything
and will come up with a unified solution.

Considering the closeness of 2019.3, and the various work that addon
authors have to do with regard to python 2 to 3 migration, additional
metadata etc, we ask you to please continue working as before the
migration from bitbucket, with the exception that all the repos are now on github.

If you can get into the habbit of topic branches, pull requests, and
reviewing each others work that would be great.

If you took the time to read the proposed workflows, thank you, we
will get back to you.

Thank you for reading.
Mesar