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, 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.
Misc
[deleted some ranting]: sorry, the earlier version(s) of my post were too harsh. I normally applaud anyone who revives an abandoned plugin, even if I do caution them to ask for naming rights or to rename to avoid trouble. But my rant was too strong, this time.
See my post here for a comparison of various of the MarkdownViewer++ alternatives in and/or submitted to Plugins Admin at this point.