Date   

Feedback wanted: add-on development and review processes documentation

 

Hello all,

A discussion arose on NVDA Add-ons mailing list regarding documentation on add-on review process. It turns out the community does have such a documentation:

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

 

As a community add-on reviewer, I’m interested in gathering feedback on this document. The goal of an upcoming documentation edit (and rename) is to strive toward friendliness – friendly toward users and add-on beginners (authors and reviewers), as well as make the process more transparent. Please either write to me directly or comment on NvDA Add-ons mailing list if you have any questions, comments, concerns, or suggestions.

Cheers,

Joseph


Alpha and Visual Studio doesn't rock well

Karl-Otto Rosenqvist
 

Hi!
I've experienced that NVDA alpha snapshots have made my life in Visual Studio 2019 harder a while now. Not sure for how long but a couple of weeks perhaps. I checked the new setting for selective UIA messages and it was true.
I installed NVDA 2020.2 and it was noticeable quicker in Visual Studio.

What is going on? Is there anything I can check and report back?


Cheers

Karl-Otto
--
Karl-Otto Rosenqvist
MAWINGU
Orgnr: 750804-3937
+46 (0)701 75 98 56
karl-otto@mawingu.se


translating the certification exam

Afik Souffir
 

 

Hi all,

 

I want to try to translate the NVDA certification exam from English to Hebrew.

 

How can I do it?

 

Afik.

 

 

 

 


NVDA 2020.3beta4 is now available for testing

Reef Turner
 

Hi all,

NVDA 2020.3beta4 is now available for testing. This is the fourth beta for the 2020.3 release, please take some time to test the release and report any issues.

Highlights and download links can be found in the release blog post at: https://www.nvaccess.org/post/nvda-2020-3beta4

Thanks!


Re: Call for testing: UI Automation in Windows Console

Bill Dengler
 

Actually, the inbox console on those builds already has many of these UIA fixes (so no need to replace your console)!

 

Bill

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Joseph Lee
Sent: Monday, 28 September 2020 20:41
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Call for testing: UI Automation in Windows Console

 

Hi,

For optimal setup, please use Windows 10 Insider Preview dev channel build 20170 or later.

Cheers,

Joseph

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Bill Dengler
Sent: Monday, September 28, 2020 5:38 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] Call for testing: UI Automation in Windows Console

 

Hi nvda-devel,

Microsoft has been doing a lot of really great work on UI Automation (UIA) in Windows Console (command prompt, PowerShell, and the Windows Subsystem for Linux). UIA vastly improves performance and stability in console, but some issues prevented it from becoming default in NVDA 2019.3.

Many of the bugs in UIA have been fixed, and I’m hoping it’ll be good enough to be default for the Windows 10 21H1 update to be released in the first half of 2021! However, it’s important that all serious bugs are resolved before UIA becomes the default. The deadline for fixes to make it into the next Windows update is 30 October 2020.

I’d really appreciate it if people tested this build (extract the zip and run OpenConsole.exe) of the Windows Console with “use UI Automation to access Windows Console” enabled in NVDA’s advanced settings and reported any issues to me. Alternatively, you can file issues on the microsoft/terminal GitHub repo (which also is used for Windows Console). If you file issues with Microsoft, please provide a test case for them to run in the NVDA Python console (see this issue as an example) and CC @carlos-zamora. If you need help generating a test case, please let me know.

To aid in testing, you can replace the Windows default console with OpenConsole. Change the owner of %systemroot%\system32\conhost.exe to yourself (in security properties), then grant you or the administrators group full control of the file. Rename conhost.exe to conhost.exe.orig, paste in OpenConsole.exe into the folder, and rename it to conhost.exe. If you’ve done it correctly, running nav.is21H1Plus in the Python console (NVDA+control+z) started from cmd should return True! To switch back to your original console, just rename conhost.exe to something else, and rename conhost.exe.orig back to conhost.exe.

 

Thanks,

Bill


Re: Call for testing: UI Automation in Windows Console

 

Hi,

For optimal setup, please use Windows 10 Insider Preview dev channel build 20170 or later.

Cheers,

Joseph

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Bill Dengler
Sent: Monday, September 28, 2020 5:38 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] Call for testing: UI Automation in Windows Console

 

Hi nvda-devel,

Microsoft has been doing a lot of really great work on UI Automation (UIA) in Windows Console (command prompt, PowerShell, and the Windows Subsystem for Linux). UIA vastly improves performance and stability in console, but some issues prevented it from becoming default in NVDA 2019.3.

Many of the bugs in UIA have been fixed, and I’m hoping it’ll be good enough to be default for the Windows 10 21H1 update to be released in the first half of 2021! However, it’s important that all serious bugs are resolved before UIA becomes the default. The deadline for fixes to make it into the next Windows update is 30 October 2020.

I’d really appreciate it if people tested this build (extract the zip and run OpenConsole.exe) of the Windows Console with “use UI Automation to access Windows Console” enabled in NVDA’s advanced settings and reported any issues to me. Alternatively, you can file issues on the microsoft/terminal GitHub repo (which also is used for Windows Console). If you file issues with Microsoft, please provide a test case for them to run in the NVDA Python console (see this issue as an example) and CC @carlos-zamora. If you need help generating a test case, please let me know.

To aid in testing, you can replace the Windows default console with OpenConsole. Change the owner of %systemroot%\system32\conhost.exe to yourself (in security properties), then grant you or the administrators group full control of the file. Rename conhost.exe to conhost.exe.orig, paste in OpenConsole.exe into the folder, and rename it to conhost.exe. If you’ve done it correctly, running nav.is21H1Plus in the Python console (NVDA+control+z) started from cmd should return True! To switch back to your original console, just rename conhost.exe to something else, and rename conhost.exe.orig back to conhost.exe.

 

Thanks,

Bill


Call for testing: UI Automation in Windows Console

Bill Dengler
 

Hi nvda-devel,

Microsoft has been doing a lot of really great work on UI Automation (UIA) in Windows Console (command prompt, PowerShell, and the Windows Subsystem for Linux). UIA vastly improves performance and stability in console, but some issues prevented it from becoming default in NVDA 2019.3.

Many of the bugs in UIA have been fixed, and I’m hoping it’ll be good enough to be default for the Windows 10 21H1 update to be released in the first half of 2021! However, it’s important that all serious bugs are resolved before UIA becomes the default. The deadline for fixes to make it into the next Windows update is 30 October 2020.

I’d really appreciate it if people tested this build (extract the zip and run OpenConsole.exe) of the Windows Console with “use UI Automation to access Windows Console” enabled in NVDA’s advanced settings and reported any issues to me. Alternatively, you can file issues on the microsoft/terminal GitHub repo (which also is used for Windows Console). If you file issues with Microsoft, please provide a test case for them to run in the NVDA Python console (see this issue as an example) and CC @carlos-zamora. If you need help generating a test case, please let me know.

To aid in testing, you can replace the Windows default console with OpenConsole. Change the owner of %systemroot%\system32\conhost.exe to yourself (in security properties), then grant you or the administrators group full control of the file. Rename conhost.exe to conhost.exe.orig, paste in OpenConsole.exe into the folder, and rename it to conhost.exe. If you’ve done it correctly, running nav.is21H1Plus in the Python console (NVDA+control+z) started from cmd should return True! To switch back to your original console, just rename conhost.exe to something else, and rename conhost.exe.orig back to conhost.exe.

 

Thanks,

Bill


Discussion: how much should add-ons depend on each other for functionality?

 

Hi all,

A discussion arose on NVDA Add-ons mailing list regarding an add-on author wanting to use features or the entirety of another add-on for certain features i.e. add-on dependence. As this list is mostly geared toward NVDA Core development, I ask that you respond to the following discussion topic on NVDA Add-ons list: to what degree can and should add-ons depend on each other for features and functionality?

Cheers,

Joseph


Re: NVDA Community Add-on Template: 2020.3 edition released, last Python 2 compatible release

Ralf Kefferpuetz
 

Sorry Joseph, I used the wrong mail before…😉

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Joseph Lee
Sent: Samstag, 26. September 2020 11:23
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-devel] NVDA Community Add-on Template: 2020.3 edition released, last Python 2 compatible release

 

Hello everyone,

NVDA Community Add-on Template 2020.3 is now available. The repo can be found at:

https://github.com/nvdaaddons/addonTemplate

 

If you are using the Add-on Template for the first time, please download the repo and apply it to your add-on. If you are already using Add-on Template as part of your add-on repo, please apply the new version whenever you are ready.

 

Changes:

  • Many lint fixes thanks to Flake8 (contributed by Lukasz Golonka).
  • Optimizations to SConstruct file: when converting Markdown to HTML, file.write call is no longer called three times; it is now called only once.

 

IMPORTANT: Add-on Template 2020.3 is the last version to be compatible with Python 2 of any kind. The next version of Add-on Template (January 2021) will require Python 3.7 or later.

 

Cheers,

Joseph


Re: NVDA Community Add-on Template: 2020.3 edition released, last Python 2 compatible release

Ralf Kefferpuetz
 

Das hier hat übrigends die Messung meiner C: SSD ergeben.

------------------------------------------------------------------------------

CrystalDiskMark 7.0.0 x64 (C) 2007-2019 hiyohiyo

                                  Crystal Dew World: https://crystalmark.info/

------------------------------------------------------------------------------

* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]

* KB = 1000 bytes, KiB = 1024 bytes

 

[Read]

Sequential 1MiB (Q=  8, T= 1):   546.198 MB/s [    520.9 IOPS] < 15311.47 us>

Sequential 1MiB (Q=  1, T= 1):   502.045 MB/s [    478.8 IOPS] <  2086.69 us>

    Random 4KiB (Q= 32, T=16):   363.257 MB/s [  88685.8 IOPS] <  5756.54 us>

    Random 4KiB (Q=  1, T= 1):    35.962 MB/s [   8779.8 IOPS] <   113.49 us>

 

[Write]

Sequential 1MiB (Q=  8, T= 1):   516.617 MB/s [    492.7 IOPS] < 16158.68 us>

Sequential 1MiB (Q=  1, T= 1):   487.699 MB/s [    465.1 IOPS] <  2147.64 us>

    Random 4KiB (Q= 32, T=16):   304.255 MB/s [  74281.0 IOPS] <  6878.49 us>

    Random 4KiB (Q=  1, T= 1):    94.108 MB/s [  22975.6 IOPS] <    43.28 us>

 

Profile: Default

   Test: 1 GiB (x5) [Interval: 5 sec] <DefaultAffinity=DISABLED>

   Date: 2020/09/27 17:43:56

     OS: Windows 10 Professional [10.0 Build 19041] (x64)

 

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Joseph Lee
Sent: Samstag, 26. September 2020 11:23
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-devel] NVDA Community Add-on Template: 2020.3 edition released, last Python 2 compatible release

 

Hello everyone,

NVDA Community Add-on Template 2020.3 is now available. The repo can be found at:

https://github.com/nvdaaddons/addonTemplate

 

If you are using the Add-on Template for the first time, please download the repo and apply it to your add-on. If you are already using Add-on Template as part of your add-on repo, please apply the new version whenever you are ready.

 

Changes:

  • Many lint fixes thanks to Flake8 (contributed by Lukasz Golonka).
  • Optimizations to SConstruct file: when converting Markdown to HTML, file.write call is no longer called three times; it is now called only once.

 

IMPORTANT: Add-on Template 2020.3 is the last version to be compatible with Python 2 of any kind. The next version of Add-on Template (January 2021) will require Python 3.7 or later.

 

Cheers,

Joseph


Re: Probably a windows query, but anyway...

Brian's Mail list account
 

Here is the part of the log concerned with this problem. Its very variable though. OK so I can reboot nvda and it will then speak, but the windows sound does not turn itself off merely due to the driver not being initialised...
DEBUG - core.main (11:35:53.978) - MainThread (2416):
Initializing tones
WARNING - tones.initialize (11:35:53.978) - MainThread (2416):
Failed to initialize audio for tones
Traceback (most recent call last):
File "tones.pyc", line 28, in initialize
File "nvwave.pyc", line 159, in __init__
File "nvwave.pyc", line 178, in open
File "nvwave.pyc", line 89, in _winmm_errcheck
FileNotFoundError: [Errno 2] A device ID has been used that is out of range for your system.
DEBUG - core.main (11:35:53.978) - MainThread (2416):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (11:35:53.978) - MainThread (2416):
Loading speech dictionary 'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (11:35:53.978) - MainThread (2416):
file 'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\default.dic' not found.
DEBUG - speechDictHandler.SpeechDict.load (11:35:53.978) - MainThread (2416):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (11:35:53.978) - MainThread (2416):
3 loaded records.
DEBUG - core.main (11:35:53.978) - MainThread (2416):
Initializing speech
ERROR - synthDriverHandler.setSynth (11:35:54.025) - MainThread (2416):
setSynth
Traceback (most recent call last):
File "synthDriverHandler.pyc", line 447, in setSynth
File "synthDriverHandler.pyc", line 418, in getSynthInstance
File "synthDrivers\espeak.pyc", line 48, in __init__
File "synthDrivers\_espeak.pyc", line 345, in initialize
File "nvwave.pyc", line 159, in __init__
File "nvwave.pyc", line 178, in open
File "nvwave.pyc", line 89, in _winmm_errcheck
FileNotFoundError: [Errno 2] A device ID has been used that is out of range for your system.
DEBUG - autoSettingsUtils.autoSettings.AutoSettings._registerConfigSaveAction (11:35:54.025) - MainThread (2416):
registering pre_configSave action: <class 'synthDrivers.silence.SynthDriver'>
DEBUG - speechDictHandler.SpeechDict.load (11:35:54.025) - MainThread (2416):
Loading speech dictionary 'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\silence\silence.dic'...
DEBUG - speechDictHandler.SpeechDict.load (11:35:54.025) - MainThread (2416):
file 'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\silence\silence.dic' not found.
DEBUG - synthDriverHandler.SynthDriver.loadSettings (11:35:54.025) - MainThread (2416):
Loaded settings for SynthDriver silence
INFO - synthDriverHandler.setSynth (11:35:54.025) - MainThread (2416):
Loaded synthDriver silence
INFO - core.main (11:35:54.025) - MainThread (2416):
Brian


bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, 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, September 24, 2020 8:42 AM
Subject: [nvda-devel] Probably a windows query, but anyway...


On occasion, my Windows 7 64 bit machine will boot up apparently with no nvda synth selected. Ie silence.
It seems that on these occasions, the audio driver has not finished initialising so you do not hear the windows or nvda start sound and when I look in the nvda log it thinks it has no sound installed so moves the synth to silence.

I have tried to find a way to make Windows always load the sound drivers first, but without much success, so I wondered if there was a switch somewhere that would force nvda to assume a sound driver was there so to speak. After all the windows sounds still work, so I'd have thought nvda should as well.
Brian

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




NVDA Community Add-on Template: 2020.3 edition released, last Python 2 compatible release

 

Hello everyone,

NVDA Community Add-on Template 2020.3 is now available. The repo can be found at:

https://github.com/nvdaaddons/addonTemplate

 

If you are using the Add-on Template for the first time, please download the repo and apply it to your add-on. If you are already using Add-on Template as part of your add-on repo, please apply the new version whenever you are ready.

 

Changes:

  • Many lint fixes thanks to Flake8 (contributed by Lukasz Golonka).
  • Optimizations to SConstruct file: when converting Markdown to HTML, file.write call is no longer called three times; it is now called only once.

 

IMPORTANT: Add-on Template 2020.3 is the last version to be compatible with Python 2 of any kind. The next version of Add-on Template (January 2021) will require Python 3.7 or later.

 

Cheers,

Joseph


NVDA 2020.3beta3 is now available for testing

Reef Turner
 

Hi all,

NVDA 2020.3beta3 is now available for testing. This is the third beta for the 2020.3 release, please take some time to test the release and report any issues.

Highlights and download links can be found in the release blog post at: https://www.nvaccess.org/post/nvda-2020-3beta3

Thanks!


Probably a windows query, but anyway...

Brian's Mail list account
 

On occasion, my Windows 7 64 bit machine will boot up apparently with no nvda synth selected. Ie silence.
It seems that on these occasions, the audio driver has not finished initialising so you do not hear the windows or nvda start sound and when I look in the nvda log it thinks it has no sound installed so moves the synth to silence.

I have tried to find a way to make Windows always load the sound drivers first, but without much success, so I wondered if there was a switch somewhere that would force nvda to assume a sound driver was there so to speak. After all the windows sounds still work, so I'd have thought nvda should as well.
Brian

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


How to debug when garbage collector finds unreachable objects

Cyrille
 

Hello

 

Since NVDA2020.3beta1, there are sometimes error messages about garbage collector finding unreachable objects.

This appears only sporadically. Do they need to be signalled?

How can I debug such errors?

 

You can find below an log example. It happened this time in Outlook Extended add-on. However it also may appear in other situations.

 

Cheers,

 

Cyrille

 

 

============================================

 

Log example:

 

IO - inputCore.InputManager.executeGesture (22:28:37.866) - winInputHook (38768):

Input: kb(desktop):alt+1

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.104) - MainThread (19412):

Garbage collector has found one or more unreachable objects. See further warnings for specific objects.

Stack trace:

  File "nvda.pyw", line 215, in <module>

  File "core.pyc", line 550, in main

  File "wx\core.pyc", line 2134, in MainLoop

  File "gui\__init__.pyc", line 1050, in Notify

  File "core.pyc", line 520, in run

  File "queueHandler.pyc", line 88, in pumpAll

  File "queueHandler.pyc", line 55, in flushQueue

  File "scriptHandler.pyc", line 166, in _queueScriptCallback

  File "keyboardHandler.pyc", line 516, in executeScript

  File "inputCore.pyc", line 201, in executeScript

  File "scriptHandler.pyc", line 208, in executeScript

  File "C:\Users\Cyrille\AppData\Roaming\nvda\addons\outlookExtended\appModules\outlook\__init__.py", line 502, in _genericScript_reportHeaderField

    return self.reportHeaderFieldN(n, gesture)

  File "C:\Users\Cyrille\AppData\Roaming\nvda\addons\outlookExtended\appModules\outlook\__init__.py", line 250, in reportHeaderFieldN

    self.olItemWindow = OutlookItemWindow(self.getRootDialog(), debug=debug)

  File "C:\Users\Cyrille\AppData\Roaming\nvda\addons\outlookExtended\appModules\outlook\itemWindow.py", line 36, in __init__

    self.windowType = [wt for wt in windowTypeList if getattr(self, 'is' + wt)()]

  File "C:\Users\Cyrille\AppData\Roaming\nvda\addons\outlookExtended\appModules\outlook\itemWindow.py", line 36, in <listcomp>

    self.windowType = [wt for wt in windowTypeList if getattr(self, 'is' + wt)()]

  File "C:\Users\Cyrille\AppData\Roaming\nvda\addons\outlookExtended\appModules\outlook\itemWindow.py", line 54, in isMessage

    return self.hasHeaderFieldsInThisOrder(lstCID)

  File "C:\Users\Cyrille\AppData\Roaming\nvda\addons\outlookExtended\appModules\outlook\itemWindow.py", line 187, in hasHeaderFieldsInThisOrder

    ls1 = [obj.windowControlID for obj in self.rootDialog.children if obj.windowControlID in lstCID]

  File "baseObject.pyc", line 42, in __get__

  File "baseObject.pyc", line 146, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\__init__.pyc", line 1065, in _get_children

  File "NVDAObjects\__init__.pyc", line 79, in __call__

  File "NVDAObjects\IAccessible\__init__.pyc", line 660, in __init__

  File "garbageHandler.pyc", line 23, in __del__

  File "garbageHandler.pyc", line 64, in notifyObjectDeletion

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.104) - MainThread (19412):

Deleting unreachable object <NVDAObjects.IAccessible.IAccessible object at 0x06426710>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.104) - MainThread (19412):

Deleting unreachable object <NVDAObjects.IAccessible.WindowRoot object at 0x040E43D0>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <NVDAObjects.window.Desktop object at 0x00FC40D0>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <NVDAObjects.IAccessible.IAccessible object at 0x07F86C50>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <NVDAObjects.IAccessible.WindowRoot object at 0x07F86730>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <NVDAObjects.IAccessible.IAccessible object at 0x07F86B30>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <NVDAObjects.IAccessible.WindowRoot object at 0x07F86C90>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <NVDAObjects.IAccessible.IAccessible object at 0x07F868B0>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <NVDAObjects.IAccessible.WindowRoot object at 0x07F86B90>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <NVDAObjects.IAccessible.IAccessible object at 0x012329B0>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <POINTER(IAccessible) ptr=0x119cbc0 at 7ccd6c0>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <POINTER(IAccessible) ptr=0x119cd20 at 123c440>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <POINTER(IAccessible) ptr=0x36e0b88 at fb1210>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <POINTER(IAccessible) ptr=0x36e0be0 at 123c210>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <POINTER(IAccessible) ptr=0x36e0c38 at fb18f0>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <POINTER(IAccessible) ptr=0x627becc at 123c580>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <POINTER(IAccessible) ptr=0x633d048 at fb1c60>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <POINTER(IAccessible) ptr=0x633d0a0 at 123c6c0>

WARNING - garbageHandler.notifyObjectDeletion (22:28:38.120) - MainThread (19412):

Deleting unreachable object <POINTER(IAccessible) ptr=0x633d0f8 at 123c3f0>

ERROR - garbageHandler._collectionCallback (22:28:38.120) - MainThread (19412):

Found at least 19 unreachable objects in run

 


NVDA 2020.3beta2 is now available for testing

Reef Turner
 

Hi all,

NVDA 2020.3beta2 is now available for testing. This is the second beta for the 2020.3 release, please take some time to test the release and report any issues.

Highlights and download links can be found in the release blog post at: https://www.nvaccess.org/post/nvda-2020-3beta2

Thanks!


Re: NVDA 2020.3beta1 is now available for testing

Noelia Ruiz
 

No problem, thank you for clarification.

Enviado desde mi iPhone

El 15 sept 2020, a las 12:36, Reef Turner <reef@nvaccess.org> escribió:

Yes, thanks Noelia. I probably should have worded the announcement slightly differently.

In addition, we believe that we have resolved the issues with downloading the beta.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Noelia Ruiz
Sent: Tuesday, 15 September 2020 9:26 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA 2020.3beta1 is now available for testing

Hi again, I have seen the announcement of NVDA 2020.3beta1 on Twitter with the verb download, so I assume that though installing it is an option, it's not recommended for most users and the mentioned recommendation posted on January 16 is still in place.
Thanks for this new beta :)

2020-09-14 15:49 GMT+02:00, Noelia Ruiz via groups.io
<nrm1977=gmail.com@groups.io>:
Hello:

In January 2020, NV Access explained that it's better to use alpha and
beta in portable or temporary copies without installation:

We recommend anyone testing prerelease builds be comfortable using
portable or temporary versions. Always keep your stable build handy,
just in case.
https://www.nvaccess.org/post/in-process-16th-january/

Is this not so valid at this stage, for example due to changes in the
release process?

Thanks

2020-09-14 14:41 GMT+02:00, Reef Turner <reef@nvaccess.org>:
Hi all,

NVDA 2020.3beta1 is now available for testing. This is the first beta
for the 2020.3 release, please install and test the release and
report any issues.

Highlights and download links can be found in the release blog post at:
https://www.nvaccess.org/post/nvda-2020-3beta1/

Thanks!











Re: NVDA 2020.3beta1 is now available for testing

Reef Turner
 

Yes, thanks Noelia. I probably should have worded the announcement slightly differently.

In addition, we believe that we have resolved the issues with downloading the beta.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Noelia Ruiz
Sent: Tuesday, 15 September 2020 9:26 AM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] NVDA 2020.3beta1 is now available for testing

Hi again, I have seen the announcement of NVDA 2020.3beta1 on Twitter with the verb download, so I assume that though installing it is an option, it's not recommended for most users and the mentioned recommendation posted on January 16 is still in place.
Thanks for this new beta :)

2020-09-14 15:49 GMT+02:00, Noelia Ruiz via groups.io
<nrm1977=gmail.com@groups.io>:
Hello:

In January 2020, NV Access explained that it's better to use alpha and
beta in portable or temporary copies without installation:

We recommend anyone testing prerelease builds be comfortable using
portable or temporary versions. Always keep your stable build handy,
just in case.
https://www.nvaccess.org/post/in-process-16th-january/

Is this not so valid at this stage, for example due to changes in the
release process?

Thanks

2020-09-14 14:41 GMT+02:00, Reef Turner <reef@nvaccess.org>:
Hi all,

NVDA 2020.3beta1 is now available for testing. This is the first beta
for the 2020.3 release, please install and test the release and
report any issues.

Highlights and download links can be found in the release blog post at:
https://www.nvaccess.org/post/nvda-2020-3beta1/

Thanks!






Re: Core code styling questions

Reef Turner
 

Hi all,

 

As Mick mentioned, we have tried to follow the pep8 recommendations as much as possible, the flake 8 config file will show where we have made exceptions. Though what has been listed in this thread seems like a good summary.

 

If the docs for linting could use further examples, please create a PR to add them. It’s a challenge to create good docs!

 

f-strings can typically be used in NVDA code, but should not be used with gettext. It simply won’t be able to look up the translation. Variables are inserted before the translation lookup happens for f-string, whereas in using string.format the format can be applied to the result of the lookup. Consider the following demo:

 

>>> def _(myString):

...     print(f"Looking up: {myString}")

...     return myString

...

>>> answer = 42

>>> _(f"the answer is {answer}")

Looking up: the answer is 42

'the answer is 42'

>>> _("the answer is {answer}").format(answer=answer)

Looking up: the answer is {answer}

'the answer is 42'

 

Hope this helps to clarify the problem.

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Joseph Lee
Sent: Thursday, 10 September 2020 10:14 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Core code styling questions

 

Hi,

No, and it is not really a good string format as it introduces security issues.

Cheers,

Joseph

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Sean
Sent: Thursday, September 10, 2020 1:07 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Core code styling questions

 

Does f-string work successfully with gettex?

I could not do that. It seems like Python cannot get f-string expressions from gettex.

On 10/09/2020 22:46, Joseph Lee wrote:

Hi,
A few months ago I did bring up this possibility for all sorts of messages,
but Mick then pointed out that there are times when an "f" string isn't
appropriate such as translations as formatted string literals can embed
Python expressions which opens up security issues and bad translation output
(and input). In the log outputs, yes, it makes sense to try standardizing
around formatted string literals, and that's the standard I have adopted
across my add-ons. 
Cheers,
Joseph
 
-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Bill Dengler
Sent: Thursday, September 10, 2020 12:40 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Core code styling questions
 
3. Percent substitutions: actually, don't use them at all. Please use 
the format method on strings. E.g. "My name is
{name}".format(name="Mick")
What about PEP498 strings? (I've used them since threshold was merged, at
least):
https://www.python.org/dev/peps/pep-0498
Bill
 
-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Luke Davis
Sent: Thursday, 10 September 2020 07:43
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Core code styling questions
 
On Thu, 10 Sep 2020, Michael Curran wrote:
 
I believe that most if not all of these stylings are from Python's
Pep8 standard.
 
I have read PEP8, but I was aware we break it in a few respects (tabs, line
lengths, not using underscores in most function names, etc.), so wasn't sure
if we had a separate project rule for any of the areas I asked about.
 
3. Percent substitutions: actually, don't use them at all. Please use 
the format method on strings. E.g. "My name is
{name}".format(name="Mick")
 
I certainly do, in my own code, but their all over the place in existing
code (addonHandler, for example, where I'm currently working).
 
I don't mind modernizing them when coming across them, but it's not exactly
linting so I didn't think to do it automatically.
 
I appreciate the response!
 
Luke
 
 
 
 
 
 
 
 
 
 
 

--
Sean

👨🦯 I’m programmer. I coding often Python, sometimes Go and rarely C++.


Re: NVDA 2020.3beta1 is now available for testing

Noelia Ruiz
 

Hi again, I have seen the announcement of NVDA 2020.3beta1 on Twitter
with the verb download, so I assume that though installing it is an
option, it's not recommended for most users and the mentioned
recommendation posted on January 16 is still in place.
Thanks for this new beta :)

2020-09-14 15:49 GMT+02:00, Noelia Ruiz via groups.io
<nrm1977=gmail.com@groups.io>:

Hello:

In January 2020, NV Access explained that it's better to use alpha and
beta in portable or temporary copies without installation:

We recommend anyone testing prerelease builds be comfortable using
portable or temporary versions. Always keep your stable build handy, just
in case.
https://www.nvaccess.org/post/in-process-16th-january/

Is this not so valid at this stage, for example due to changes in the
release process?

Thanks

2020-09-14 14:41 GMT+02:00, Reef Turner <reef@nvaccess.org>:
Hi all,

NVDA 2020.3beta1 is now available for testing. This is the first beta for
the 2020.3 release, please install and test the release and report any
issues.

Highlights and download links can be found in the release blog post at:
https://www.nvaccess.org/post/nvda-2020-3beta1/

Thanks!





301 - 320 of 45574