Date   

Re: ColumnReview issue with Task manager

Cyrille
 

Hi Alberto
Below is the part of the log when I open the task manager and try to select the first list item. Task manager opens directly with the detailed view since I have clicked the "More details" button last time I have opened the task manager. This setting is remembered when I launch it again.
...
# Comment: launching task manager
IO - inputCore.InputManager.executeGesture (10:32:28.078) - winInputHook (7928):
Input: kb(desktop):shift+control+escape
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:32:28.089) - MainThread (16040):
Cancelling
DEBUGWARNING - watchdog._watcher (10:32:28.747) - watchdog (15700):
Trying to recover from freeze, core 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 514, in run
  File "IAccessibleHandler.pyc", line 915, in pumpAll
  File "IAccessibleHandler.pyc", line 772, in processForegroundWinEvent
  File "IAccessibleHandler.pyc", line 539, in winEventToNVDAEvent
  File "NVDAObjects\IAccessible\__init__.pyc", line 42, in getNVDAObjectFromEvent
  File "IAccessibleHandler.pyc", line 347, in accessibleObjectFromEvent
  File "oleacc.pyc", line 265, in AccessibleObjectFromEvent

DEBUG - IAccessibleHandler.accessibleObjectFromEvent (10:32:29.032) - MainThread (16040):
oleacc.AccessibleObjectFromEvent with window 1249212, objectID -4 and childID 0:
IO - speech.speak (10:32:30.490) - MainThread (16040):
Speaking [LangChangeCommand ('fr_FR'), 'Gestionnaire des tâches']
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:32:30.490) - MainThread (16040):
Begin processing speech
IO - speech.speak (10:32:30.593) - MainThread (16040):
Speaking [LangChangeCommand ('fr_FR'), 'Liste d’éléments', 'grille de données']
IO - speech.speak (10:32:30.703) - MainThread (16040):
Speaking [LangChangeCommand ('fr_FR'), 'Liste d’éléments', 'liste']
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:32:31.213) - Dummy-1 (1412):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:32:31.213) - Dummy-1 (1412):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:32:31.313) - Dummy-1 (1412):
Queue empty, done processing
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:32:32.770) - MainThread (16040):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:32:33.745) - Dummy-2 (1984):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:32:33.745) - Dummy-2 (1984):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:32:33.845) - Dummy-2 (1984):
Queue empty, done processing
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:32:33.977) - MainThread (16040):
Begin processing speech
DEBUG - synthDrivers.oneCore.SynthDriver._callback (10:32:34.745) - Dummy-1 (1412):
Done pushing audio
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:32:34.745) - Dummy-1 (1412):
Calling idle on audio player
DEBUG - synthDrivers.oneCore.SynthDriver._processQueue (10:32:34.845) - Dummy-1 (1412):
Queue empty, done processing
# Comment: Trying to select the first item in the list
IO - inputCore.InputManager.executeGesture (10:32:35.025) - winInputHook (7928):
Input: kb(desktop):downArrow
DEBUG - synthDrivers.oneCore.SynthDriver.cancel (10:32:35.035) - MainThread (16040):
Cancelling
ERROR - NVDAObjects.__call__ (10:32:36.683) - Dummy-3 (19044):
Exception in chooseNVDAObjectOverlayClasses for <'taskmgr' (appName 'taskmgr', process ID 10052) at address 8df3170>
Traceback (most recent call last):
  File "NVDAObjects\__init__.pyc", line 95, in __call__
  File "appModules\taskmgr.pyc", line 31, in chooseNVDAObjectOverlayClasses
  File "baseObject.pyc", line 42, in __get__
  File "baseObject.pyc", line 145, in _getPropertyViaCache
  File "NVDAObjects\UIA\__init__.pyc", line 1266, in _get_presentationType
  File "baseObject.pyc", line 42, in __get__
  File "baseObject.pyc", line 145, in _getPropertyViaCache
  File "NVDAObjects\__init__.pyc", line 741, in _get_presentationType
  File "baseObject.pyc", line 42, in __get__
  File "baseObject.pyc", line 145, in _getPropertyViaCache
  File "NVDAObjects\UIA\__init__.pyc", line 1200, in _get_states
  File "NVDAObjects\UIA\__init__.pyc", line 823, in _prefetchUIACacheForPropertyIDs
  File "comtypesMonkeyPatches.pyc", line 26, in __call__
ctypes.ArgumentError: argument 1: <class 'RecursionError'>: maximum recursion depth exceeded in __instancecheck__
# Comment: The log ends here and NVDA crashes.
The strange thing is that the error does not show anything of your add-on. However, a clean NVDA does not crash, whereas with columnReview it does.
The test was done on a portable 2019.3.1 with only columnReview installed.
Note that the first freeze occurs also without columnReview.
Do you have an idea?
Did you succeed in reproducing this issue by using the mmore detailed view of task manager?
Cheers,
Cyrille
----- Mail d'origine -----
De: Alberto Buffolino <a.buffolino@...> end of the log
À: nvda-addons@nvda-addons.groups.io
Envoyé: Fri, 07 Feb 2020 15:00:15 +0100 (CET)
Objet: Re: [nvda-addons] ColumnReview issue with Task manager
Cyrille via Groups.Io, il 06/02/2020 22.55, ha scritto:
> On NVDA 2019.3rc3, ColumnReview add-on makes task manager crash NVDA.
> Did you experience this?
Alberto:
Hi Cyrille,
uh, sorry, I use classic task manager, so I never noticed it. Does
nvda-old.log contain useful errors? In case, can you send me?
Alberto


Re: Getting a complete list of colors NVDA has on file

James Scholes
 

No, because colour naming in NVDA isn't based on a simple lookup table. Instead, RGB values are converted to hue, saturation and value. A calculation is then performed to work out the:

* closest shade on the scale from white to black (e.g. white, light grey, black);
* the closest hue (red, orange-yellow, aqua-blue, etc.);
* closest applicable brightness categorisation based on saturation (very dark, dark pale, etc.); and
* if appropriate, the most specific brown hue if the color is within certin parameters.

I suppose you could force NVDA to calculate a name for all 16777216 possible RGB permutations in a brute-force approach and then store the lot. But there would be crossover between colours which were similar enough that they had the same name, making for duplicate entries.

Regards,

James Scholes

On 10/02/2020 at 6:16 pm, Andy B. wrote:
Hi,
Is there a way to obtain a list of RGB objects representing all the colors NVDA knows about? I need this for the next part of my project.


Getting a complete list of colors NVDA has on file

Andy B.
 

Hi,

Is there a way to obtain a list of RGB objects representing all the colors NVDA knows about? I need this for the next part of my project.


Re: NVDA addon creation development environment #addon

Andy B.
 

Hi,

Right now it is impossible to have add-ons use autocomplete in an editor/IDE. As mentioned, parts of NVDA aren't running or loaded yet. For example, how is a non working copy of NVDA (the source) going to know what add-ons the current running copy (portable/installed) is running at the time? This is the problem we run into with creating development environments. Tests might work, but the unit tests have to be installed in the working copy. An earlier thread proved that NVDA tries to cut down the amount of weight it has to carry around, so this might not work. However, NVDA could make an add-on that contains the tests. It could then be installed in the current working copy without forcing everyone to download a heavy installer. We could then write add-on tests against the tests add-on by importing its namespaces/modules, then disconnect the tests from the production version of the add-on. An easier way for now is to use the nvda python terminal to test your add-on code. In fact, Developer toolkit was written entirely in the nvda python terminal before getting put into files. In other words, Developer toolkit's features are tested one by one in the nvda python terminal before they are put into testing/production. I even went so far as to test color conversion and pairing routines in the nvda python terminal. I know my idea works before my research is complete.


On Mon, Feb 10, 2020 at 6:10 PM James Scholes <james@...> wrote:
I don't think this is going to work the way you want.  When you say:

 > cloned nvda-vscode into the root of that folder under .vscode

... I assume you're referring to this:
https://github.com/nvaccess/vscode-nvda

But AFAIK, that is only for development of NVDA itself, rather than add-ons.

I've been out of the loop for a while, so someone can correct me if I'm
wrong.  But my understanding is that to date, nobody has created a
method of accessing and testing NVDA-specific Python modules without a
running copy of the screen reader.  Even if they had, several parts of
NVDA depend on others which cannot yet be instantiated outside of the
context of a running copy.  That may change in the future, or someone
may come up with mocked objects for testing purposes.

In terms of your test module not appearing to be present, it's because
code is no longer loaded from %appdata%\roaming\nvda\appModules.  You'll
need to enable the developer scratchpad in Settings -> Advanced, and
then use %appdata%\roaming\nvda\scratchpad\appModules instead.

In many ways, NVDA add-on development is still in its infancy.  Nobody
does TDD, for example, because there isn't yet a way to facilitate it.
The same extends to support within an IDE.  Contributions in this arena
are very much welcome though!

Regards,

James Scholes

On 10/02/2020 at 3:46 pm, Florian Beijers wrote:
> Hi,
>
> So first, if this isn't the place to ask this question, please let me
> know. It seemed the most suitable, but I might have missed a resource :)
>
> I am trying to create a development environment for creating addons
> based on Visual Studio Code. I am running into a bit of a snag though,
> hoping someone here might know what I am missing. My steps:
>
> - recursively cloned nvaccess/nvda
> - cloned nvda-vscode into the root of that folder under .vscode
> - Opened the folder using file -> open folder... in Visual Studio Code
> Insiders.
> - As a test, I wanted to build the notepad.py example in the developer
> guide to see if intellisense and such would come up. So I added
> %appdata%\roaming\nvda\appModules to the workspace.
> - Selected my python interpreter as being python 3.8.1 32-bit within the
> global scope for both folders in the workspace, this setting invoked
> through a gesture appears to be folder-specific rather than workspace-wide.
> - Created a new file within appModules called notepad.py with the
> following content:
>
>
> import appModuleHandler
>
> class AppModule(appModuleHandler.AppModule):
> pass
>
> After doing all this, these are my observations:
>
> - The visual studio code problems view reports appModuleHandler could
> not be imported.
> - Similarly, autocomplete does not come up for NVDA-specific options.
> - My appModule is not loaded according to nvda+ctrl+f1. However, that
> could have to do with the pass statement, does that unload the module?
>
> A few questions:
>
> - Does anyone see something obvious I might have missed?
> - When I run scons source to prepare the source tree, scons tells me it
> can't find python 3.7-32. This is true, I don't have that specific
> version of Python installed. Is that why this is happening?
> - Am I on completely the wrong track and can I get NVDA's python context
> into VS Code some other way?
>
> Thanks a bunch for any help :)
>




Re: NVDA addon creation development environment #addon

James Scholes
 

I don't think this is going to work the way you want. When you say:

cloned nvda-vscode into the root of that folder under .vscode
... I assume you're referring to this:
https://github.com/nvaccess/vscode-nvda

But AFAIK, that is only for development of NVDA itself, rather than add-ons.

I've been out of the loop for a while, so someone can correct me if I'm wrong. But my understanding is that to date, nobody has created a method of accessing and testing NVDA-specific Python modules without a running copy of the screen reader. Even if they had, several parts of NVDA depend on others which cannot yet be instantiated outside of the context of a running copy. That may change in the future, or someone may come up with mocked objects for testing purposes.

In terms of your test module not appearing to be present, it's because code is no longer loaded from %appdata%\roaming\nvda\appModules. You'll need to enable the developer scratchpad in Settings -> Advanced, and then use %appdata%\roaming\nvda\scratchpad\appModules instead.

In many ways, NVDA add-on development is still in its infancy. Nobody does TDD, for example, because there isn't yet a way to facilitate it. The same extends to support within an IDE. Contributions in this arena are very much welcome though!

Regards,

James Scholes

On 10/02/2020 at 3:46 pm, Florian Beijers wrote:
Hi,
So first, if this isn't the place to ask this question, please let me know. It seemed the most suitable, but I might have missed a resource :)
I am trying to create a development environment for creating addons based on Visual Studio Code. I am running into a bit of a snag though, hoping someone here might know what I am missing. My steps:
- recursively cloned nvaccess/nvda
- cloned nvda-vscode into the root of that folder under .vscode
- Opened the folder using file -> open folder... in Visual Studio Code Insiders.
- As a test, I wanted to build the notepad.py example in the developer guide to see if intellisense and such would come up. So I added %appdata%\roaming\nvda\appModules to the workspace.
- Selected my python interpreter as being python 3.8.1 32-bit within the global scope for both folders in the workspace, this setting invoked through a gesture appears to be folder-specific rather than workspace-wide.
- Created a new file within appModules called notepad.py with the following content:
import appModuleHandler
class AppModule(appModuleHandler.AppModule):
pass
After doing all this, these are my observations:
- The visual studio code problems view reports appModuleHandler could not be imported.
- Similarly, autocomplete does not come up for NVDA-specific options.
- My appModule is not loaded according to nvda+ctrl+f1. However, that could have to do with the pass statement, does that unload the module?
A few questions:
- Does anyone see something obvious I might have missed?
- When I run scons source to prepare the source tree, scons tells me it can't find python 3.7-32. This is true, I don't have that specific version of Python installed. Is that why this is happening?
- Am I on completely the wrong track and can I get NVDA's python context into VS Code some other way?
Thanks a bunch for any help :)


NVDA addon creation development environment #addon

Florian Beijers
 

Hi,

So first, if this isn't the place to ask this question, please let me know. It seemed the most suitable, but I might have missed a resource :)

I am trying to create a development environment for creating addons based on Visual Studio Code. I am running into a bit of a snag though, hoping someone here might know what I am missing. My steps:

- recursively cloned nvaccess/nvda
- cloned nvda-vscode into the root of that folder under .vscode
- Opened the folder using file -> open folder... in Visual Studio Code Insiders.
- As a test, I wanted to build the notepad.py example in the developer guide to see if intellisense and such would come up. So I added %appdata%\roaming\nvda\appModules to the workspace.
- Selected my python interpreter as being python 3.8.1 32-bit within the global scope for both folders in the workspace, this setting invoked through a gesture appears to be folder-specific rather than workspace-wide.
- Created a new file within appModules called notepad.py with the following content:


import appModuleHandler

class AppModule(appModuleHandler.AppModule):
    pass

After doing all this, these are my observations:

- The visual studio code problems view reports appModuleHandler could not be imported.
- Similarly, autocomplete does not come up for NVDA-specific options.
- My appModule is not loaded according to nvda+ctrl+f1. However, that could have to do with the pass statement, does that unload the module?

A few questions:

- Does anyone see something obvious I might have missed?
- When I run scons source to prepare the source tree, scons tells me it can't find python 3.7-32. This is true, I don't have that specific version of Python installed. Is that why this is happening?
- Am I on completely the wrong track and can I get NVDA's python context into VS Code some other way?

Thanks a bunch for any help :)


Re: Release: Outlook Extended 1.5-dev-20200209

Cyrille
 

Thanks, all is OK.

Cyrille

-----Message d'origine-----
De : nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> De la part de Noelia Ruiz
Envoyé : lundi 10 février 2020 21:10
À : nvda-addons@nvda-addons.groups.io
Objet : Re: [nvda-addons] Release: Outlook Extended 1.5-dev-20200209

Hi Cyrille, I have updated the link for the dev version as requested.
Please check it.
Cheers

2020-02-10 17:18 GMT+01:00, Noelia Ruiz via Groups.Io
<nrm1977=gmail.com@groups.io>:
Hi Cyrille, OK, I will perform a last check and will post the link
provided by you in addonFiles to be published on the website.
About tuples, OK, I will use tuples when they aren't mutable, as done
in NVDA, but it's not important.
About pull requests, I think that this list is good for general
feedback, announcements, reporting bugs and so on for people who don't
have a GitHub account and discussion about particular things to know
if they are really bugs or not, before opening an issue.
Generally I make pull requests in my personal repo, even when none is
going to review it, for reference and give the chance of a review.
pcKbBrl is not in the add-ons organization, and for this reason I
asked you to review in my personal repo.
I think that really, when one is familiarized with GitHub, it's easier
to perform reviews there. For example I have mentioned a full stop,
but on GitHub I may commented the specific line and even suggest you
the right change, that you may apply.
Anyway for now it's not needed.
Going to home now and will post your add-on. If you have any questions
before, let me know.
Cheers

2020-02-10 14:49 GMT+01:00, Cyrille via Groups.Io
<cyrille.bougot2=laposte.net@groups.io>:
Hi Noelia

Thanks for your feedback.
I have updated the readme to fix missing full stop as welle as other
grammar or typo errors. I have also added the change for version 1.5
in change log.
I did not generate another test release since only the readme has
been modified,so you can see the result on the Github repo page.

Regarding the series of items (lists or tuples), I usually use list
because I do not care so much if they are mutable or not. Also some
data series (list or tuple) may not be mutable in normal use cases
but it may be handy to have them mutable on debug purpose. In any
case, I do not think that it will change the performances since the
number of times these lists are used is small.
See this page for more information regarding list/tuples perf
benchmarking:
http://zwmiller.com/blogs/python_data_structure_speed.html
And specifically this conclusion:
"I think the conclusion here is that if you need to create millions
and millions of small python structures (like if you're importing
from a SQL database row-by-row) a tuple may actually have some
performance advantages."If you disagree with this choice, let's discuss it of course.

At least, regarding PR's, I am not so convinced to use it for now
since the process is not yet clear to me. And also because I imagine
that people read more the comments in the e-mails of this list than
comments in a PR.
Anyway
I am not totally opposed to this. If you have further comments, I may
open a PR so that you comment there. Just let me know what kind of PR
I should
do:
should I do CyrilleB79/OutlookExtended/master ->
nvdaaddons/OutlookExtended/master?
This is different from the PR's you opened since we are on a dev version.
For PcKbBrl review, the dev version was already reviewed informally
on the list), and I just had to make a last check, as well as
confirming that no other problem had arisen meanwhile.

Cheers,

Cyrille






----- Mail d'origine -----De: Noelia Ruiz <nrm1977@...>&Agrave;:
nvda-addons@...&eacute;: Mon, 10 Feb 2020
06:46:10
+0100 (CET)Objet: Re: [nvda-addons] Release: Outlook Extended
1.5-dev-20200209

Hi Cyrille, i have reviewed diffs locally.If you (and others) are
comfortable using pull requests, it maybefaster to make suggestions.
We can post the add-on on the website.Anyway, I have seen that after
the word "again" in readme there is nota full stop (dot .), but it
appears after other similar items. Also, Isee several lists in the
code and I am not sure if they can bereplaced by tuples or if you use
list since they are mutable.Now I will go to job. Not sure if other
admins are available.Otherwise I can post the add-on after job.I
don't know if we should grant access again to add-on files to
peoplenow, since I don't know if they will be used in the workflow
and maybeextra work, and I don't know if after that access should be
removedagain. I would like to ask Mesar, and in the meantime we
admins cantake charge of this.Admins are owners, that is, Joseph as
the main owner, creator of theorganization, Mesar and me.Cheers

2020-02-10 0:01 GMT+01:00, Cyrille via
Groups.Io<cyrille.bougot2=laposte.net@groups.io>:> Hello>>>> Here is
a new release for Outlook Extended.>> This release contains 2
bugfixes for NVDA
2019.3 compatibility:>> * Fixes error in information bar reading> *
Fixes table navigation in address book results>>>> Direct download
link:>>
https://github.com/CyrilleB79/outlookExtended/releases/download/V1.5-
dev-202> 00209/outlookExtended-1.5-dev-20200209.nvda-addon>>>>
@admins:>> Please update the download link on the website (get.php).
Thanks.>>>> Cheers,>>>>
Cyrille>>>>> >>









Vocalizer 2.1.0 Ad-on pops in compact voices

piotr machacz
 

Hi all,
This message is mainly for Rui but I'd also like to know if anyone else is seeing this.

I just updated to NVDA 2019.3 and took the time to update my ad-ons. Since Vocalizer Expressive (the Tiflotecnia one) isn't ported yet I grabbed the updated version of the Vocalizer 2 driver on the Portuguese site on tiflotecnia.net, plus a handful of old favorite voices (All the English compact ones to use Serena, plus Polish Agata and English Lee in premium).

I'm finding that the 2 premium voices work great. However, the compact voices have audio glitches. It's as if the audio cuts out occasionally for a few milisecond and comes back which causes a slight stutter and sometimes clicks and pops in the audio. These stutters also seem to be consistent and always happen at the same point in a sentence. To reproduce, simply switch to a voice like Karen or Serena, and navigate around the NVDA menu, adjust voice parameters like volume and listen to how the numbers are spoken.

I'm fairly sure I don't remember the voices behaving this badly on older NVDA versions as I used to use them pretty regularly, my computer is also pretty powerful (Core I7-6700 and NVDA is running from an SSD so performance shouldn't be a problem)

Is anyone else seeing this?


Re: TeamSpeak add-on update, and NVDA 2019.3 anomaly

Quentin Christensen
 

Doug, how did you go with updating your TeamSpeak add-on?  We had someone enquire about TeamSpeak support.  I found your add-on at  https://www.dlee.org/teamspeak/NVDA/ although I think that's still the Python 2.x version (NVDA 2019.2.1 and earlier?)

Regards

Quentin.

On Mon, Jan 13, 2020 at 12:07 AM Doug Lee <nvda@...> wrote:
I tried to update the TeamSpeak NVDA add-on I maintain to support NVDA 2019.3; but as indicated in the following Twitter announcement, I ran into a problem which I will better detail below.

The announcement:

Status of NVDA #nvda3 Python 3 add-on for TeamSpeak:
NVDA 2019.3 beta, even with add-ons disabled, does not work at all on my machine while TeamSpeak 3.3.2.0 is in focus. Even NVDA+n does not work there.
Work on this add-on is suspended pending resolution of this oddity.

Details:

Once TeamSpeak takes focus:
* NVDA+t says nothing.
* Tab and Shift+Tab say nothing.
* NVDA+n says nothing.
* Alt+Tab works to get focus out of TeamSpeak, after which things in NVDA return to normal.
* This applies even if I start NVDA 2019.3 with add-ons disabled.
* This does not occur at all in NVDA 2019.2.
* No log entries appear during all of the above odd behavior.

I suspect keyboard handler issues in NVDA 2019.3 itself, but that's a guess. I'm writing here to find out if anyone else has encountered something like this under the beta NVDA version.

I should mention that TeamSpeak 3.3.2.0 is written against Qt 5.12.3, which uses UIA rather than MSAA as was done in older Qt versions.


--
Doug Lee                 dgl@...                http://www.dlee.org
Level Access             doug.lee@...    http://www.LevelAccess.com
"The most exciting phrase to hear in science, the one that heralds
new discoveries, is not 'Eureka!' ('I found it!') but rather 'hmm....
that's funny...'"  --   Isaac Asimov





--
Quentin Christensen
Training and Support Manager



Re: Noelia's add-ons: compatible with NVDA 2019.3 #addonrelease

 

Just got the ones I needed to go downloaded.

Its good to see that a lot of people if they havn't done so are ready to go.

I am waiting for 1 addon I use and another one which I don't use as much and while it will be a pitty if it all doesn't go to plan its not like the end of the world with half my supports gone which is good.

I am also happy that I chose sapi synths over nvda addons as it seems there is a lot of issues going on right now but its only been the first day.

I think the devs should be congratulated on this, everything was done to make sure everyone had time to get things going.

Granted there will be those that havn't or just are not going to but if there are repos maybe community can make these things work again.

On 11/02/2020 9:16 am, Noelia Ruiz wrote:
Hi, I have released and posted on the website the following stable add-ons:
- clipContentsDesigner 11.0, coauthor: Abdel.
- emoticons 12.0: main author: Chris LM. Other authors: Mesar,
Francisco Javier Estrada and me.
- eMule 4.0: coauthors: Chris LM and Alberto Buffolino.
- PC Keyboard Braille Input 2019.1. Author: NV Access (Jamie).
Maintained by me and contributed by people mentioned in readme,
reviewed by Cyrille.
- placeMarkers 14.0: coauthor: Chris LM.
- readFeeds 9.0. Coauthor: Mesar.
- reportSymbols 5.0.
- reportPasswords 1.0, project independent from similar add-on named
speakPasswords, also posted on the website.

All these require NVDA 2019.3 or later.
Thanks all, users, translators and other contributors.
Cheers


Re: SwitchSynth 1.03

Nikola Jovic
 

Thank you very much, one of a few addons I was missing.

On 2/10/20, Tyler Spivey <tspivey@...> wrote:
Should work with Python 2 and 3.



https://github.com/tspivey/switchSynth/releases/download/v1.03/switchSynth-1.03.nvda-addon





SwitchSynth 1.03

Tyler Spivey
 


Noelia's add-ons: compatible with NVDA 2019.3 #addonrelease

Noelia Ruiz
 

Hi, I have released and posted on the website the following stable add-ons:
- clipContentsDesigner 11.0, coauthor: Abdel.
- emoticons 12.0: main author: Chris LM. Other authors: Mesar,
Francisco Javier Estrada and me.
- eMule 4.0: coauthors: Chris LM and Alberto Buffolino.
- PC Keyboard Braille Input 2019.1. Author: NV Access (Jamie).
Maintained by me and contributed by people mentioned in readme,
reviewed by Cyrille.
- placeMarkers 14.0: coauthor: Chris LM.
- readFeeds 9.0. Coauthor: Mesar.
- reportSymbols 5.0.
- reportPasswords 1.0, project independent from similar add-on named
speakPasswords, also posted on the website.

All these require NVDA 2019.3 or later.
Thanks all, users, translators and other contributors.
Cheers


Re: Release: Outlook Extended 1.5-dev-20200209

Noelia Ruiz
 

Hi Cyrille, I have updated the link for the dev version as requested.
Please check it.
Cheers

2020-02-10 17:18 GMT+01:00, Noelia Ruiz via Groups.Io
<nrm1977=gmail.com@groups.io>:

Hi Cyrille, OK, I will perform a last check and will post the link
provided by you in addonFiles to be published on the website.
About tuples, OK, I will use tuples when they aren't mutable, as done
in NVDA, but it's not important.
About pull requests, I think that this list is good for general
feedback, announcements, reporting bugs and so on for people who don't
have a GitHub account and discussion about particular things to know
if they are really bugs or not, before opening an issue.
Generally I make pull requests in my personal repo, even when none is
going to review it, for reference and give the chance of a review.
pcKbBrl is not in the add-ons organization, and for this reason I
asked you to review in my personal repo.
I think that really, when one is familiarized with GitHub, it's easier
to perform reviews there. For example I have mentioned a full stop,
but on GitHub I may commented the specific line and even suggest you
the right change, that you may apply.
Anyway for now it's not needed.
Going to home now and will post your add-on. If you have any questions
before, let me know.
Cheers

2020-02-10 14:49 GMT+01:00, Cyrille via Groups.Io
<cyrille.bougot2=laposte.net@groups.io>:
Hi Noelia

Thanks for your feedback.
I have updated the readme to fix missing full stop as welle as other
grammar
or typo errors. I have also added the change for version 1.5 in change
log.
I did not generate another test release since only the readme has been
modified,so you can see the result on the Github repo page.

Regarding the series of items (lists or tuples), I usually use list
because
I do not care so much if they are mutable or not. Also some data series
(list or tuple) may not be mutable in normal use cases but it may be
handy
to have them mutable on debug purpose. In any case, I do not think that
it
will change the performances since the number of times these lists are
used
is small.
See this page for more information regarding list/tuples perf
benchmarking:
http://zwmiller.com/blogs/python_data_structure_speed.html
And specifically this conclusion:
"I think the conclusion here is that if you need to create millions and
millions of small python structures (like if you're importing from a SQL
database row-by-row) a tuple may actually have some performance
advantages."If you disagree with this choice, let's discuss it of course.

At least, regarding PR's, I am not so convinced to use it for now since
the
process is not yet clear to me. And also because I imagine that people
read
more the comments in the e-mails of this list than comments in a PR.
Anyway
I am not totally opposed to this. If you have further comments, I may open
a
PR so that you comment there. Just let me know what kind of PR I should
do:
should I do CyrilleB79/OutlookExtended/master ->
nvdaaddons/OutlookExtended/master?
This is different from the PR's you opened since we are on a dev version.
For PcKbBrl review, the dev version was already reviewed informally on
the
list), and I just had to make a last check, as well as confirming that no
other problem had arisen meanwhile.

Cheers,

Cyrille






----- Mail d'origine -----De: Noelia Ruiz <nrm1977@...>&Agrave;:
nvda-addons@...&eacute;: Mon, 10 Feb 2020 06:46:10
+0100 (CET)Objet: Re: [nvda-addons] Release: Outlook Extended
1.5-dev-20200209

Hi Cyrille, i have reviewed diffs locally.If you (and others) are
comfortable using pull requests, it maybefaster to make suggestions. We
can
post the add-on on the website.Anyway, I have seen that after the word
"again" in readme there is nota full stop (dot .), but it appears after
other similar items. Also, Isee several lists in the code and I am not
sure
if they can bereplaced by tuples or if you use list since they are
mutable.Now I will go to job. Not sure if other admins are
available.Otherwise I can post the add-on after job.I don't know if we
should grant access again to add-on files to peoplenow, since I don't
know
if they will be used in the workflow and maybeextra work, and I don't
know
if after that access should be removedagain. I would like to ask Mesar,
and
in the meantime we admins cantake charge of this.Admins are owners, that
is,
Joseph as the main owner, creator of theorganization, Mesar and me.Cheers

2020-02-10 0:01 GMT+01:00, Cyrille via
Groups.Io<cyrille.bougot2=laposte.net@groups.io>:> Hello>>>> Here is a
new
release for Outlook Extended.>> This release contains 2 bugfixes for NVDA
2019.3 compatibility:>> * Fixes error in information bar reading> * Fixes
table navigation in address book results>>>> Direct download link:>>
https://github.com/CyrilleB79/outlookExtended/releases/download/V1.5-dev-202>
00209/outlookExtended-1.5-dev-20200209.nvda-addon>>>> @admins:>> Please
update the download link on the website (get.php). Thanks.>>>>
Cheers,>>>>
Cyrille>>>>> >>









Welcome to the NVDA Community Add-ons website - PC Keyboard Braille Input for NVDA #feed

nvda-addons@nvda-addons.groups.io Integration <nvda-addons@...>
 

PC Keyboard Braille Input for NVDA

  • Author: NV Access Limited, Noelia Ruiz Martínez
  • Copyright: 2012-2019 NV Access Limited, Noelia Ruiz Martínez
  • License: GNU General Public License version 2.0
  • Download: stable version (compatible with NVDA 2019.3 or later)
  • Download: development version (compatible with NVDA 2019.3 or later)
  • version 2014.1 (compatible with NVDA 2017.3 to 2019.2)

This NVDA add-on allows braille to be entered via the PC keyboard. Currently, the following keyboard layouts are supported:

  • English QWERTY keyboard.
  • French (France).
  • German (Germany).
  • Italian (Italy).
  • Persian.
  • Portuguese (Portugal).
  • Spanish (Spain and Mexico).
  • Turkish.

How to configure

The add-on can be configured from its category in the NVDA's settings dialog, under NVDA's menu, Preferences submenu. A gesture for opening the add-on settings panel can be assigned from Input gestures dialog, configuration category.

Check the corresponding checkbox if you want to type using only one hand, or ensure it's not checked if you prefer to type using the standard mode (two hands).

How to Use

  1. Press NVDA+0 to enable braille input. This gesture can be changed from Input gestures dialog, Braille category.
  2. Type braille by pressing keys together on the PC keyboard as if it were a braille keyboard.
    • If you want to enter text using two hands, use the following keys if you work with a QWERTY English keyboard, or the keys located at the corresponding positions in other layouts:
      • f, d and s for dots 1, 2 and 3 respectively.
      • j, k and l for dots 4, 5 and 6 respectively.
      • Use the keys a and ; (semi-colon) for dots 7 and 8, respectively.
      • You can also use the keys on the row above; i.e. q, w, e, r, u, i, o and p.
    • If you want to type text using one hand, you can compose characters pressing keys simultaneously or in several keystrokes, adding the dots corresponding to the desired character. Press g or h to type the character when you have added all its dots. If you make a mistake building a character, you can clear the dots before typing it by pressing t or y. The keys used in QWERTY English keyboard are the following:
      • Left hand: f, d, s, r, e, w, a, q for dots 1, 2, 3, 4, 5, 6, 7 and 8.
      • Right hand: j, k, l, u, i, o, ; (semicolon), p for dots 1, 2, 3, 4, 5, 6, 7 and 8.
  3. You can press most other keys as normal, including space, backspace, enter and function keys. Take care about not pressing alt+shift, since changing the keyboard layout may affect the entered dots.
  4. Press NVDA+0 to disable braille input.

Important Notes

This add-on uses NVDA's in-built braille input support. Therefore, the input table used is that specified in NVDA's Braille Settings dialog.

Some keyboards, particularly laptop keyboards, cannot handle certain combinations of keys being pressed. When this happens, certain keys are simply ignored. Unfortunately, there is nothing that can be done to fix this, as the keys are simply never received by Windows or NVDA. In some cases, using the upper row of keys with either or both hands might help, as your keyboard may allow these keys.

Contributors

  • James Teh
  • Noelia.
  • Mohammadreza Rashad
  • Cagri Dogan
  • Bernd Dorer
  • Ângelo Abrantes
  • Cyrille Bougot
  • Abdel.


Welcome to the NVDA Community Add-ons website - Report Passwords #feed

nvda-addons@nvda-addons.groups.io Integration <nvda-addons@...>
 

Report Passwords

This add-on adds the option of speaking the text typed on protected controls like passwords, such as when logging into web-based email sites, where typed characters are spoken as asterisks.

Note: NVDA has an option to configure if typed passwords will be spoken on Windows terminals. This add-on won't affect that kind of controls, where typed characters in passwords can be read or silenced, but won't be spoken as asterisks.

How to configure

The add-on can be configured from its category in the NVDA's settings dialog, under NVDA's menu, Preferences submenu. A gesture for opening the add-on settings panel can be assigned from Input gestures dialog, configuration category.

Tip: If you aren't used to configure NVDA to speak typed characters or words and want to hear typed text in passwords, you may create a configuration profile to enable the speaking of typed characters and passwords, and assign it to a gesture or create a trigger to enable it automatically in certain situations. For convenience, NVDA will ask if you want to set a dedicated profile when the add-on is installed.

Changes for 1.0

  • Initial version.


Re: New add-on proposal: Color wheel

Jim Homme
 

Hi,

For convenience, is it possible that the user could somehow send colors from the Developer Toolkit to the Color Wheel addon? This would be very cool. We would not have to go through the steps of firing up the Color Wheel addon and inputting the color. I envision it working so that you press a key, NVDA fires puts the colors somewhere that the Color Wheel addon can find it, NVDA runs the Color Wheel addon. The addon checks the location. If it sees the colors, it does whatever it needs to.

 

Thanks.

 

Jim

 

 

==========

Jim Homme

Digital Accessibility

Bender Consulting Services

412-787-8567

https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions

 

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Andy B. via Groups.Io
Sent: Monday, February 10, 2020 6:03 AM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] New add-on proposal: Color wheel

 

Hi,

 

To complement Developer toolkit, I am going to create another add-on called color wheel. Color wheel will come separately because some people might have a need for a color wheel, but not have a need for developer tools. Color wheel will have the following initial features:

 

* Find the complement for a specific color

* Find the split complement for a specific color.

* Find the analogous colors for a specific color.

* Browse a list of available colors to start with (still researching this point).

* Choose a color to start with by entering its RGB, HSV, HEX, or name values.

* Copy the chosen color scheme to the clipboard in the form of RGB, HSV, HEX, or name values.

 

To come later: square, rectangle, triadic color schemes.

 

What do you think?

 

 


Re: About speechHistory add-on

James Scholes
 

I've just merged Abdel's pull request:
https://github.com/jscholes/nvda-speech-history/pull/4

If there are issues with that code, please either:

1. comment on that pull request so that Abdel can rectify them;
2. create a new issue and CC @abdel792 so that he is notified; or
3. fix the issues yourself and submit a PR of your own.

I use this add-on every day myself, and want it to be ready for users of NVDA 2019.3 as soon as possible. Unfortunately, I'm also snowed under with other work, and haven't been keeping up with the latest developments in the NVDA add-ons world or infrastructure.

At this point, I'm asking for community input and assistance to fix anything which needs fixing, configure anything that needs configuring, and get a new version out the door. If there is anything I need to do on my end as the repository owner, please let me know the precise steps and I will do them. My thanks to Abdel for his input and work so far.

Regards,

James Scholes

On 10/02/2020 at 6:52 am, DaVid wrote:
Hi! What is the current situation with this add-on? Many users need this add-on.
I encountered an issue with the updated version by abdel, and solved it. I didn't report it yet on github because I don't know what gonna happen with this add-on. Is urgent to solve the situation since the stable 2019.3 version of NVDA was released now.
Regards,
David CM
Ingeniero en computación (ITCR)
Experto certificado en NVDA. <https://certification.nvaccess.org/>
correo: dhf360@... <mailto:dhf360@...>
Encuentra mis proyectos libres en github. <https://github.com/davidacm/>
y las publicaciones en mi canal de youtube. <https://www.youtube.com/channel/UCYnnJZQLYHd7g0R3UcJ9-lg>
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@... <http://programacionaccesible+subscribe@...>
O participa en Programación accesible en Facebook. <https://facebook.com/groups/235117436637120>
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@... <http://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. <https://facebook.com/groups/590594451020594>
También puedes hacer tus consultas sobre tu lector de pantallas favorito en la comunidad de NVDA en español (facebook) <https://facebook.com/groups/298402187029900>
El vie., 27 dic. 2019 a las 4:50, Abdel (<abdelkrim.bensaid@... <mailto:abdelkrim.bensaid@...>>) escribió:
Hi Noelia,
Thank you so much.
At the moment, there is nothing I can do until I have the approval of
James Sholes, I have not yet received his response.
I have just created a new commit in the Fork so that the add-on repo
complies with the addonTemplate, which should allow construction with
the scons command.
This updated structure also makes it possible to comply with the
requirements of the translation system.
You can clone this job by executing the following command, the work is
in the addonTemplate branch:

> git clone https://github.com/abdel792/speechHistory.git
Thanks again for everything.
Kind regards,
Abdel.
Le 27/12/2019 à 10:52, Noelia Ruiz a écrit :
> Hi Abdel and all, Mesar has told me that he will work on this today
> and he will ask me if he has any question on which I can help.
> So for now let's wait before creating the repo on Bitbucket, since
> maybe it's not needed.
> Cheers
>
> 2019-12-26 18:29 GMT+01:00, Abdel <abdelkrim.bensaid@...
<mailto:abdelkrim.bensaid@...>>:
>> Hi Noelia,
>>
>> Thanks for these good news.
>>
>> I, too, think it preferable that NVDA's translation system is on
GitHub,
>> instead of Bitbucket.
>>
>> Kind regards,
>> Abdel.
>>
>> Le 26/12/2019 à 17:44, Noelia Ruiz a écrit :
>>> Hi Abdel, a repo is not created for this.
>>> While James and Tyler can reply, please let me try to contact
Mesar.
>>> As you know, GitHub is more accessible than Bitbucket and the
system
>>> is complex. For example, I think it would be better to fork a
repo in
>>> the add-ons organization and moving the translations system to
GitHub.
>>> Mesar Hameed, the creator of this system, forked placeMarkers
to the
>>> add-ons organization to test how add-ons could be translated using
>>> GitHub instead of Bitbucket.
>>> Hi is very busy, but let me wait for some days or try to
contact him
>>> again in case he can move the system to GitHub before creating the
>>> repo on Bitbucket. At least I wish to ask him to borrow work if
>>> possible.
>>> Not sure if he can answer quickly or when. Please be patient.
He said
>>> me that he would try to contact me over Christmas to complete this
>>> task.
>>> Thanks
>>>
>>> 2019-12-26 16:03 GMT+01:00, Abdel <abdelkrim.bensaid@...
<mailto:abdelkrim.bensaid@...>>:
>>>> Hi all,
>>>>
>>>> @James:
>>>>
>>>> A Pull Request is pending on the GitHub repo of the speechHistory
>>>> add-on:
>>>>
>>>>> https://github.com/jscholes/nvda-speech-history/pull/4
>>>> If you agree, you can merge it.
>>>>
>>>> @Noelia:
>>>>
>>>> Is there a repo on Bitbucket for this add-on?
>>>>
>>>> If Tyler and James agree, I suggest that a repo on bitbucket
be created
>>>> so that this add-on is linked to the translation system.
>>>>
>>>> Thanks.
>>>>
>>>> Kind regards,
>>>> Abdel.
>>>>
>>>> Le 25/12/2019 à 12:48, Abdel a écrit :
>>>>> Hi Nicolas,
>>>>>
>>>>> Thanks for your test.
>>>>>
>>>>> Try this fix, the download link is the same:
>>>>>
>>>>>> http://cyber25.free.fr/nvda-addons/speechHistory.nvda-addon
>>>>> I just added a space in line 35 for Python versions greater
than 2, as
>>>>> follows:
>>>>>
>>>>>>       text = u''.join([x for x in sequence if isinstance(x,
>>>>>> basestring)]) if sys.version_info.major == 2 else u'
'.join([x for x
>>>>>> in sequence if isinstance(x, str)])
>>>>> Does this fix the bug for you?
>>>>>
>>>>> Kind regards,
>>>>> Abdel.
>>>>>
>>>>> Le 25/12/2019 à 11:19, Nikola Jovic a écrit :
>>>>>> Hello. Thanks for your work. I'm facing a small issue with
this addon
>>>>>> under python 3 releases of NVDA which can be noticed if you
try to
>>>>>> copy any text from a GUI. For example, if you copy the
keyboard combo
>>>>>> box in the NVDA keyboard settings dialog, the output looks
like this:
>>>>>> Keyboard layout:combo boxlaptopcollapsedAlt+k. Normally
there should
>>>>>> of course be a space between the control label and it's
role. Under
>>>>>> 2019.2.1 for example, this same output looks like this: Keyboard
>>>>>> layout:  combo box  desktop  collapsed  Alt+k
>>>>>>
>>>>>> On 12/25/19, Abdel <abdelkrim.bensaid@...
<mailto:abdelkrim.bensaid@...>> wrote:
>>>>>>> Hi James, Joseph and all,
>>>>>>>
>>>>>>> @James:
>>>>>>>
>>>>>>> Don't worry, we're here to help each other.
>>>>>>>
>>>>>>> If you allow me, I could help you make the speechHistory add-on
>>>>>>> compatible nvda-2019.3, there is not much to do.
>>>>>>>
>>>>>>> You just have to add the import of the sys module and
modify line 35
>>>>>>> as
>>>>>>> follows:
>>>>>>>
>>>>>>> From:
>>>>>>>
>>>>>>>>        text = u''.join([x for x in sequence if isinstance(x,
>>>>>>>> basestring)])
>>>>>>> To:
>>>>>>>
>>>>>>>>        text = u''.join([x for x in sequence if isinstance(x,
>>>>>>>> basestring)]) if sys.version_info.major == 2 else
u''.join([x for x
>>>>>>>> in
>>>>>>>> sequence if isinstance(x, str)])
>>>>>>> The basestring type doesn't exist with Python 3.
>>>>>>>
>>>>>>> It will also be necessary to define minimumNVDAVersion in the
>>>>>>> manifest
>>>>>>> file and set lastTestedNVDAVersion to 2019.3.0.
>>>>>>>
>>>>>>> Optionally, it will also be preferable to define tab as
indentation,
>>>>>>> Joseph and Noelia have always advised me to do it.
>>>>>>>
>>>>>>> For the documentation of the add-on, it is absent, it would be
>>>>>>> necessary
>>>>>>> to take that appearing on the community website.
>>>>>>>
>>>>>>> The local folder is also missing, it should be added, in
order to add
>>>>>>> the documentation of the used scripts to translate.
>>>>>>>
>>>>>>> I think I have forgotten nothing, do not hesitate to tell me if
>>>>>>> something is missing.
>>>>>>>
>>>>>>> Download link of the version tested with nvda-2019.3beta1,
I have not
>>>>>>> yet added the local folder, nor the documentation:
>>>>>>>
>>>>>>>> http://cyber25.free.fr/nvda-addons/speechHistory.nvda-addon
>>>>>>> Thanks.
>>>>>>>
>>>>>>> Kind regards,
>>>>>>> Abdel.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>
>


StationPlaylist and Windows 10 App Essentials 20.02 #addonrelease

 

Hi all,

 

StationPlaylist and WintenApps 20.02 will be released tonight (Pacific time). Both add-ons require NVDA 2019.3 or later. Also, starting from 20.02, Windows 10 App Essentials drops support for Windows 10 Version 1809 (October 2018 Update) and gains support for Version 2004.

 

Also, regarding old add-ons from me: download links for older releases compatible with NVDA 2019.2.1 will be removed no later than March 15, 2020.

Cheers,

Joseph


Re: Release: Outlook Extended 1.5-dev-20200209

Noelia Ruiz
 

Hi Cyrille, OK, I will perform a last check and will post the link
provided by you in addonFiles to be published on the website.
About tuples, OK, I will use tuples when they aren't mutable, as done
in NVDA, but it's not important.
About pull requests, I think that this list is good for general
feedback, announcements, reporting bugs and so on for people who don't
have a GitHub account and discussion about particular things to know
if they are really bugs or not, before opening an issue.
Generally I make pull requests in my personal repo, even when none is
going to review it, for reference and give the chance of a review.
pcKbBrl is not in the add-ons organization, and for this reason I
asked you to review in my personal repo.
I think that really, when one is familiarized with GitHub, it's easier
to perform reviews there. For example I have mentioned a full stop,
but on GitHub I may commented the specific line and even suggest you
the right change, that you may apply.
Anyway for now it's not needed.
Going to home now and will post your add-on. If you have any questions
before, let me know.
Cheers

2020-02-10 14:49 GMT+01:00, Cyrille via Groups.Io
<cyrille.bougot2=laposte.net@groups.io>:

Hi Noelia

Thanks for your feedback.
I have updated the readme to fix missing full stop as welle as other grammar
or typo errors. I have also added the change for version 1.5 in change log.
I did not generate another test release since only the readme has been
modified,so you can see the result on the Github repo page.

Regarding the series of items (lists or tuples), I usually use list because
I do not care so much if they are mutable or not. Also some data series
(list or tuple) may not be mutable in normal use cases but it may be handy
to have them mutable on debug purpose. In any case, I do not think that it
will change the performances since the number of times these lists are used
is small.
See this page for more information regarding list/tuples perf benchmarking:
http://zwmiller.com/blogs/python_data_structure_speed.html
And specifically this conclusion:
"I think the conclusion here is that if you need to create millions and
millions of small python structures (like if you're importing from a SQL
database row-by-row) a tuple may actually have some performance
advantages."If you disagree with this choice, let's discuss it of course.

At least, regarding PR's, I am not so convinced to use it for now since the
process is not yet clear to me. And also because I imagine that people read
more the comments in the e-mails of this list than comments in a PR. Anyway
I am not totally opposed to this. If you have further comments, I may open a
PR so that you comment there. Just let me know what kind of PR I should do:
should I do CyrilleB79/OutlookExtended/master ->
nvdaaddons/OutlookExtended/master?
This is different from the PR's you opened since we are on a dev version.
For PcKbBrl review, the dev version was already reviewed informally on the
list), and I just had to make a last check, as well as confirming that no
other problem had arisen meanwhile.

Cheers,

Cyrille






----- Mail d'origine -----De: Noelia Ruiz <nrm1977@...>&Agrave;:
nvda-addons@...&eacute;: Mon, 10 Feb 2020 06:46:10
+0100 (CET)Objet: Re: [nvda-addons] Release: Outlook Extended
1.5-dev-20200209

Hi Cyrille, i have reviewed diffs locally.If you (and others) are
comfortable using pull requests, it maybefaster to make suggestions. We can
post the add-on on the website.Anyway, I have seen that after the word
"again" in readme there is nota full stop (dot .), but it appears after
other similar items. Also, Isee several lists in the code and I am not sure
if they can bereplaced by tuples or if you use list since they are
mutable.Now I will go to job. Not sure if other admins are
available.Otherwise I can post the add-on after job.I don't know if we
should grant access again to add-on files to peoplenow, since I don't know
if they will be used in the workflow and maybeextra work, and I don't know
if after that access should be removedagain. I would like to ask Mesar, and
in the meantime we admins cantake charge of this.Admins are owners, that is,
Joseph as the main owner, creator of theorganization, Mesar and me.Cheers

2020-02-10 0:01 GMT+01:00, Cyrille via
Groups.Io<cyrille.bougot2=laposte.net@groups.io>:> Hello>>>> Here is a new
release for Outlook Extended.>> This release contains 2 bugfixes for NVDA
2019.3 compatibility:>> * Fixes error in information bar reading> * Fixes
table navigation in address book results>>>> Direct download link:>>
https://github.com/CyrilleB79/outlookExtended/releases/download/V1.5-dev-202>
00209/outlookExtended-1.5-dev-20200209.nvda-addon>>>> @admins:>> Please
update the download link on the website (get.php). Thanks.>>>> Cheers,>>>>
Cyrille>>>>> >>