i Command Not Working

[rxcube]

On a new Windows 10 Enterprise PC, newly installed python 3.10, natlink 5.4.4, dragonfly2 - all the same versions I was using successfully, and following all my instructions which work fine on my last PC to install everything and configure well - but now when using the i command to provide detailed printout of natlink info from the cli (command line interface) .exe file of natlink, the i command causes the command line interface window to close? Is this a new bug? Other commands work but not this one. The natlinkconfig_cli.exe window closes immediately now when doing that command in it.

[LexiconCode]

As I haven't developed the natlinkconfig_cli.exe I can't say for certain what's going on. However try calling natlinkconfig_cli.py via the absolute path with your python interpreter. That way you can get a look at the trace back.

[rxcube]

I would need instructions to do what you're saying. Open this, type that, etc. otherwise I don't know how to do what you said.

[LexiconCode]

I would need instructions to do what you're saying. Open this, type that, etc. otherwise I don't know how to do what you said.

One of the other project maintainers figured out the problem. This should be fixed next release.

I would recommend for now downgrading. The following commands 'python -m pip install natlinkcore==5.3.8' or 'python -m pip install natlinkcore==5.3.7'

[rxcube]

I didn't realize there were multiple project maintainers - I am only familiar with the other person I interacted with on here who is the main programmer. I am assuming you are one of the core programmers too then? To clarify - You mean the next release of Natlink? Meaning - once Natlink is > (greater than) version 5.4.4 this will be fixed?

[LexiconCode]

I didn't realize there were multiple project maintainers.

@dougransom and @quintijn are the primary maintainers. I try to help out where I can.

To clarify - You mean the next release of Natlink? Meaning - once Natlink is > (greater than) version 5.4.4 this will be fixed?

Natlink used to be monolithic and now is split into two repositories Natlink (pyd) c++ interface which is registered with dragon. NatlinkCore which is loaded by the pyd and initializes the rest of the code..

NatlinkCore can be updated independently of Natlink. Natlink repository bundles Natlink and NatlinkCore into an installer.

So I think you can get your system working by downgrading NatlinkCore or you can wait for the next natlink installer.

[rxcube]

OK, I think I understand what you mean I think about downgrading, but am I understanding correctly that we're talking about it being fixed once the current version of Natlink 5.4.4 is replaced by something newer than that 5.4.4 version, right?

[LexiconCode]

OK, I think I understand what you mean I think about downgrading, but am I understanding correctly that we're talking about it being fixed once the current version of Natlink 5.4.4 is replaced by something newer than that 5.4.4 version, right?

No I think I can be fixed now by downgrading natlinkcore as the CLI worked fine previously. Normally I would recommend to see utilizing the previous version of the installer but it would live pip install the latest natlinkcore

You're right though it would also be fixed if Natlink 5.4.5 was released and it would be fixed as well in the installer.

[quintijn]

Our main concern at the moment are several problems with the introduction of Dragon 16. There is close to release a version of natlink (to be installed via the inno setup installer or via an experimental install procedure of LexiconCode, using a python virtual environment).

Further discussion here: https://github.com/dictation-toolbox/natlink/issues/176 and (more recent) in https://github.com/dictation-toolbox/natlink/issues/196

[quintijn]

Hello, I want to close this issue. When it persists in a new release of natlink/natlinkcore, please revive it.