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 propose a few changes in the doc files, natlink/docs/faq.md (will push to PR).
For this documentation site, the menu could be "flatter", so you get "Install" and "Migrate legacy scripts" immediately when you open the site.
Moreover, natlink.playString is valid again, as it just runs via dtactions.sendkeys.sendkeys('abc')
Possibly more comments to follow.
Aaron, hopefully we can do the installer and the pip things of other packages in the coming week...
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 wasNATLINK_USERDIR.I propose a few changes in the doc files,
natlink/docs/faq.md(will push to PR).For this documentation site, the menu could be "flatter", so you get "Install" and "Migrate legacy scripts" immediately when you open the site.
Moreover,
natlink.playStringis valid again, as it just runs viadtactions.sendkeys.sendkeys('abc')Possibly more comments to follow.
Aaron, hopefully we can do the installer and the pip things of other packages in the coming week...