Quintijn Hoogenboom

let pylint recognise functions from the _natlink(...).pyd

1

Currently, pylint gives an E1101 error message when functions from natlink are called. Eg. natlink.playString. We thought that the file _natlink_core.pyi played a role in this. Could this be sorted...

This was a not very much used function of natlink. Especially when things were moving, often in "exclusive mode", (in unimacro grammar _repeat and in the originalsamplegrammars _mous.py), a (changing)...

make playEvents obsolete for Dragon16

3

Nobody seems to be able to implement natlink.playEvents into python. Let us declare this function obsolete with Dragon 16.

playEvents to be reimplemented via Python for Dragon16

5

The playEvents (and also playString) functions, as implemented in C++ with the natlink.pyd file (since 1999!) don't work any more this way. See also issue 176. (https://github.com/dictation-toolbox/natlink/issues/176) playString is now...

still elevation problems with pipping packages...

5

I think, we need to do all pip installs elevated, or none (after natlink itself). part of messages window just now: `Natlink Version: 5.5.7 Natlink pyd path: C:\Program Files (x86)\Natlink\site-packages\natlink\_natlink_core.pyd...

Doc changes with new release of Natlink/natlinkcore August 2024

2

With the upcoming release of Natlink, and also natlinkcore, the env variable to optionally define the directory for the natlink settings has been changed into `NATLINK_SETTINGSDIR`. This was `NATLINK_USERDIR`. I...

Installer problems

2

I was trying our new (not yet published) installer, I think it is going to be natlink 5.5.7. The automatic install of python3.10 32 bit did not work. I have...