Changement could impact plugins for Javascript



  • Javascript internal management has been changed in the recent releases. That means it may impact some plugins for Javascript.

    For the plugin authors: in order to make your plugins work in the future Notepad++ releases, if you use the API like NPPM_GETBUFFERLANGTYPE, NPPM_SETBUFFERLANGTYPE, NPPM_GETCURRENTLANGTYPE and/or NPPM_GETCURRENTLANGTYPE, please use L_JAVASCRIPT instead of L_JS, and update Notepad++ API header in your project here:
    https://github.com/notepad-plus-plus/notepad-plus-plus/blob/master/PowerEditor/src/MISC/PluginsManager/Notepad_plus_msgs.h



  • @donho Do newer versions completely deprecate L_JS all together? In order to make a plugin backwards compatible, would a plugin have to first check the N++ version with NPPM_GETNPPVERSION and if it is less than v6.8.4 use L_JS and if it is v6.8.4 and greater, use L_JAVASCRIPT?



  • @dail said:

    In order to make a plugin backwards compatible, would a plugin have to first check the N++ version with NPPM_GETNPPVERSION and if it is less than v6.8.4 use L_JS and if it is v6.8.4 and greater, use L_JAVASCRIPT?

    Yes, that’s right. L_JS is used for embeded javascript so only internal use in Notepad++.


Log in to reply