Release v1.7.29.0

The API workaround is not backwards compatible due to the technical limitations of Notepad++ plugin distribution model. Thus CS-Script enables/disables the workaround depending on the detected version of Notepad++. Meaning that the user experience is seamless, all versions of Notepad++ prior v8.3.0 disable the workaround, while v8.3.1 and higher enable it.

Please be aware that Notepad++ team does not coordinate their releases with the plugin authors so you may find that the future Notepad++ releases may become broken, thus if you see a specific future version of Notepad++ is crashing when you try to use CS-Script, please report it and a hotfix will become available very quickly.

You can always overwrite the auto-enabling API workaround algorithm by setting environment variable

• CSSCRIPT_NPP_NEW_NPP_API= "true" - new API enabled
• CSSCRIPT_NPP_NEW_NPP_API= "false" - new API disabled
• CSSCRIPT_NPP_NEW_NPP_API=<not set> - new API will be enabled if Npp is v8.3.1 and higherd

Huge thank you to rdipardo for the investigation and the actual solution.

Note: this release has been tested on Notepad++ v8.2.1 and v8.3.1

Changes

v1.7.29

• Added transparent switching to the new NPP API depending on the version: v8.2.1<->v8.3.0 (triggered by #64 and #65) Note: the trigger has been changed from v8.3.1 to v8.3.0 due to the N++ team decision to declare v8.3.0 as a current critical release.

v1.7.28 The major feature of this release is the workaround breaking API changes introduced in at least v8.3.1 of Notepad++.

• Patched NppPluginNet: CharacterRange.cpMin and CharacterRange.cpMax changed from int to IntPtr This addresses the problems triggered by this the third-party component (NppPluginNet):
  • Issue #64: Creating a new script crashes latest 64-bit Notepad++ release
  • Issue #65: Intermittent crashes (and the culprit is CS-Script)
• Added logging syntaxer internal errors to the plugin log dir.