David Gausmann

Hi Alan, I've made some tests and found a way to reproduce that issue. But unfortunately it is nothing that I can fix and it was there in each version of Notepad++ and the ActiveX plugin. Due to security limitations of Windows and COM, processes, which are running with Administrator privileges, are not allowed to communicate with non-Administrator processes by default. I guess that your Autocad/Briscad is running with Administrator privileges and your Notepad++ not (or vice versa). Please ensure...

Hi Alan, I've made some tests and found a way to reproduce that issue. But unfortunately it is nothing that I can fix and it was there in each version of Notepad++ and the ActiveX plugin. Due to security limitations of Windows and COM processes, which are running with Administrator privileges are not allowed to communicate with non-Administrator processes by default. I guess that your Autocad/Briscad is running with Administrator privileges and your Notepad++ not (or vice versa). Please ensure that...

Hi Alan, ok, I guess you are starting Notepad++ by calling CreateObject("NotepadPlusPlus.Application") from Autocad/Briscad and then Notepad++ starts, opens the Embedding file and then does nothing? This sounds for me as though the plugin isn't loaded anymore. The external application can start Notepad++ via COM because the registry entries are still there, but after Notepad++ has been loaded there is no communication between both applications, because newly started Notepad++ process doesn't say...

Hi Alan, I've tested the plugin with the current version but it works for me. Can give me some information what doesn't work? Do you access Autocad/Briscad from Notepad++ or vice versa? Do you have an example script? With the currently given information, I can't do anything for you...

Exception while running script as default script 1

I've closed it.

Hi Marcus, I've fixed this and uploaded version 1.1.8.7. There was a bug when executing external files. The byte order mark wasn't determined correctly. The file has been treated as ANSI instead. Because the BOM isn't valid VBScript there was the error message. Kind Regards David Gausmann

x64 version of the plugin