Practical feedback
When I tried the “undock” button, it crashed the plugin (giving an error message included in a screenshot) –
[image: 1795294404964-mv-wv2.error.png]
well, maybe the plugin hasn’t crashed, but that action didn’t work, anyway, because it is not showing the undocked window as expected, but Notepad++ was still running. If I re-start Notepad++ after that error, it started with the panel undocked; this is highly repeatable for me. If I CONTINUE after the crash, and toggle the view of the panel, it displays, and for that run, undock and dock will work. Continued experiments show that if it starts undocked (through that button being used the previous time), then the dock/undock button toggle works right; but if it starts a run docked and I click the “undock” button, it will show that error and not show the undocked window until I tell it to show the preview again (or restart Notpead++). This is bad user experience.
Second, when it’s successfully undocked via the button, I cannot use the normal Notepad++ docking panel behavior of dragging it to an edge to re-dock. OTOH, if I don’t use the button, but undock by the normal Notepad++ dragging, then I can drag it back to docked just fine. And if I make the mistake of dragging-to-undock, then clicking the button that’s still labled “undock”, it will crash not just the plugin but the entire Notepad++ application. If you’re going to call the feature “dock/undock”, it needs to work the same as the Notepad++ dock/undock, otherwise, it will cause confusion. So, other than breaking normal plugin-docking procedure, what does that button gain you that the normal dragging does not? If it’s just the button, could you make it compatible with the normal dock/undock, so it’s just two alternative ways to get exactly the same compatible result?
Philosophical feedback
Just because the code is open-source doesn’t mean the name is freely available. In general, if you’re going to take over an existing piece of software and develop it from your own fork, you either need to get permission to use the name (like what happened with PythonScript and some other plugins), or give it a new name.
I will admit, there are a couple plugins here where someone took over, including the original name, without permission, and I didn’t complain when it happened; but that was on plugins where no-one else had shown an interest in developing that plugin or a replacement, and my opinion has shifted somewhat since those days: I better understand that there are implied trademarks when a unique name is used consistently for a product, and they are legally enforceable, though without the strength of protection of registered trademarks; you can use the ™ sign to indicate you are treating a word as your trademark, without registering it, but you do not need to. And I’d say that nea being the sole user of that name from 2017 to 2026 (even if they didn’t have new releases, until they “archived” their repo, they were advertising to the world that the name for that product belonged to them) is a good indication that it probably has some implied trademark protection at this point.
So, if you’re going to continue development/support on your plugin, I’d highly recommend either getting nea’s official permission to use the name (so that you don’t find a whole slew of other people also taking your current approach, and just appropriating the name, and publishing competing forks of MarkdownViewer++ with their own version numbering, making it impossible for anyone to help anyone), or rename your project to something else.
However…
Is it needed?
See my post here. I just don’t see a need for a dozen different WebView2 clones of MarkdownViewer++, all made with AI (often the same model), all doing essentially the same thing, with tiny tweaks in the look and feel.
And sorry, but based on my couple minutes with each, so far, yours isn’t the best of the bunch.