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

Hi all,

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

How can I do it?

Afik.

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

Bill

Hi,

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

Cheers,

Joseph

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

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

Sorry Joseph, I used the wrong mail before…😉

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)

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

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

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.