1

Closed

Not compatible with Notepad++ v6.8.3

description

Initialization fails after installing, with incompatibility error.

file attachments

Closed Apr 13, 2016 at 1:44 PM by oleg_s

comments

oleg_s wrote Oct 5, 2015 at 11:22 PM

It's not a NPP compatibility problem but something else. The clean PC installation seems to be OK:

Image

Can you please elaborate on what are the exact symptoms?
What is the error message?
Did you try to reinstall the plugin?

Thanks you.

atoi wrote Oct 11, 2015 at 12:26 PM

I installed and reinstalled the plugin both through NPP's "Plugin Manager" repository itself and manually unpacking the package in .\plugins directory of NPP.

Here's the error before NPP loading the main window. I took a snapshot (attached with this comment.)

_Failed to load

This plugin is not compatible with current version of Notepad++.

Do you want to remove this plugin from plugins directory to prevent this message from the next launch time?_

oleg_s wrote Oct 13, 2015 at 6:29 AM

The message N++ is displaying is a generic message and it's not necessarily based on any plugin compatibility analysis. It only indicates definitively that the plugin for what ever reason failed to initialize.

Despite that fact that it says "This plugin is not compatible with current..." most likely it has nothing to do the compatibility as such and the screenshot in my previous email is the indication that this version of N++ is in fact compatible with the plugin.

Anyway, since I had no other reports I have to assume that somehow in your environment the plugin cannot initialize for non compatibility reasons.

I just prepared a Beta release v1.0.45.1 that has an extra error handling, which will display the message box with the exception details of the plugin initialization failure:
 MessageBox.Show("Initialization failure: " + exception, "CS-Script");
Can you please test this build on your PC and let me know if the error message is displayed and what is the message content. If it does't then it is N++ who is not loading the plugin. If it does then it is the plugin who "catching the fire".

Unfortunatelly it is a Beta release so you will need to install it manually. You will find the release in the download section (https://csscriptnpp.codeplex.com/releases/view/617889).