Well, that was at least part of the problem.

It seems as if the “Plugin Manager” is not part of the 64-bit version, but it IS part, and displaying properly, as part of the 32-bit version.

I will attempt to test printing of these documents… But, because of the storm here in Florida, it may need to wait until I’m actually back in the office… :P

A critical bugfix for v0.5.0 has been released.

IMO, it is really a stretch to think (or hope) that functionality, once embedded in a (popular) plug-in, will ever go “native”/“integrated”. There are just too many other things that the mainline developers want to get accomplished; they don’t want to spend the time to reinvent the wheel.

FYI, some improvements are in the make, see @Dave-Brotherstone’s comment here.

I’m not sure. I’m not saying it is impossible though, just don’t know how.

@Edward-Starski

don’t know if you know that you can define it yourself.

Goto Settings->Style Configurator->CSS->IDENTIFIER and add it to the user defined keywords.

If it is just to inform that it is missing open an issue here.

Cheers
Claudia

Something to keep in mind first of all is that if you just want to debug your own plugin’s code it is not necessary to build Notepad++ yourself. What I do for my plugins is create a post-build event that copies my DLL into the Notepad++ directory and then runs the notepad++.exe as the application for debugging. I can then step through my code, etc.

In theory as long as the SciLexer.dll is next to notepad++.exe then it should work. The only thing I’d suggest is make sure you build them the same, e.g. 32bit/64bit/release/debug but it sounds like you are aware of the differences. I’ve always just stuck to 32bit without boost and haven’t had issues. If it is something specific to 64bit the maybe someone else can suggest some things to try.