• PlantUML version updated to 1.2024.8
• Removed dependency to PlantUml.Net library
• Removed dependency to Fizzler library
• Added generated file information to support built in %filename() and %dirpath() preprocessor functions
• Fixed diagram background not set e.g. if white

You can download it at the 1.8.0.12 release or just wait to the next Notepad++ update to get it with the plugin manager.

relative paths are possible as well. So for me, the following works: …\Java\jre1.8.0_361\bin\java.exe. The path is resolved relative to the notepad++.exe. So if your Java JRE is parallel to the Notepad++ folder, this should do the trick.

BR, Philipp

happy to hear you like it.
You are lucky, a few weeks ago, I’ve commited a change where I changed the way Java is detected. Previously, the environment variable was checked only. Since a lot of devices are not set up with the corresponding environment variable (JAVA_PATH), I’ve added a registry detection as well.
It is not officially released yet, but have a look at the following build: PlantUmlViewer/9022421474
If Java is installed, it should be detected automatically by leaving the setting empty.
Let me know if this works for you.

BR, Philipp

• PlantUML version updated to 1.2024.3
• Set generation working directory to current file to allow relative includes
• SVG.NET library updated to 3.4.7, dependent ExCSS library updated to 4.2.3 to fix SVG export namespace prefix not set accordingly

You can download it at the 1.7.0.11 release or just wait to the next Notepad++ update to get it with the plugin manager.

SysML V2 file

Hi Andy,
obviously the diagram can’t be rendered by PlanUML. Since you are not showing a minimal set of data you want to render, its nearly impossible to say whats the reason for the error.
But a guess from my side: Keep in mind PlantUML is not SysML. Most propably the SysML standard you are talking about is not supported by PlantUML.

• PlantUML version updated to 1.2023.10
• Added option to open the file after export
• Added tooltip with potential generation error message to bottom status
• Ignored non expected generation content due to Java accessibility hooks output like PowerAutomate
• Fixed Notepad++ may freezes if plugin is docked out and looses focus
• Fixed potential generation errors after a generation failed due to Plant UML executable issues

Download it at https://github.com/Fruchtzwerg94/PlantUmlViewer, it should be also available via the plugin manager soon.

• PlantUML version 1.2023.0
• Fluent and dark style icons
• Updated to common zoom and scroll behaviour Ctrl + mouse wheel to zoom and (Shift +) mouse wheel to scroll vertically and horizontally
• New include option
• Diagram text can be included to exported SVG images
• Disabled buttons are grayed out
• … and many more

Feel free to get in touch if you have some feedback.

with the latest changes, the plugin version 1.4.0.8 is now officially available.
Biggest change is the multi page support:

Also, PlantUML was updated to 1.2022.8, an error message for non UTF-8 documents was added, the file name of generated diagram is shown in the status bar and the plugin colors are automatically updated if Notepad++ colors are changed.

Have fun with it and let me know if there are questions, problems or feedback.

Cheers,
Philipp

after some more investigation it seems like I can already come up with a first solution here. I’ve updated the current implementation to support pages as well. It’s not tested deeply but it’s worth a try. With the latest change you are able to navigate pages like shown here:

It’s not yet released officially so you need download the version to test here:
Added support for multiple pages per document Continuous Integration #63

Would be great if you could do some deeper tests. Please have a look at it and give me some feedback / let me know if it works for you.

BR

I would assume that you have a 32-bit Notepad++ (from placement in x86) and you are trying to load a 64-bit plugin.

Programs and their DLLs (a plugin is a DLL) must match in bitness.

• Enabled generation of formulas
• Added support for multiple diagrams per document
• Fixed using the text of the selected document in split mode
• A lot of UI improvements (like icons, new buttons, …)

Feel free to get in touch in case of feedback (or other things)!

Since I’ve got some very positive feedback and requests, I’ve created a new release of the plugin. It is now possible to export SVG files as well. Also the usability was improved by adding a context menu. Some small fixes are also included.

You can find the latest release here: PlantUmlViewer 1.2.0.6

Feel free to contact me for feedback, issues or requests.

Cheers,
Philipp

Thanks for these points. These points are great input, sorry for the confusion here. I’ve created a patch and released it already. Therefore I’ve removed the shortcut completely, which is indeed the most straight forward solution.
So version 1.1.1.5 should be fine regarding this.
Let me know if you see more things which could be improved!

Cheers

Or also an option in the plugin itself?

When OP said this, I was thinking of like some sort of first-running “Add this plugin’s keyboard shortcuts to N++?” question, at which point, if the user said yes, the plugin would do it behind the scenes. It could even list out the ones that it would create. (Although, if there are conflicts, what to do…?) Thus it wouldn’t be for the plugin author to recreate a mini-shortcut-mapper in their plugin.

Perhaps the only advantage in any of this would be for users that have zero idea the Shortcut Mapper even exists.

I stand by that the best advice is to not do anything custom with shortcuts in a plugin, and put those things that benefit from having a keyboard shortcut in the plugin’s main menu (per Peter).

remove the default shortcut from code and let the user do it completely by its own in the Shortcut Manager of Notepad++. Or also an option in the plugin itself?

Any command in your plugin’s main menu will be visible by Shortcut Mapper, so you don’t need to do anything special. If you wanted, you could also add the ability to turn on a shortcut in your plugin, but since that interface already exists in Shortcut Mapper, that seems a lot of extra work for you.