You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A forum user asked a while ago why N++'s built-in Docking Manager never reloads the MarkdownViewer++ panel when the application starts. This goes for NppMarkdownPanel as well, and for the same reason, so I'm cross-posting nea/MarkdownViewerPlusPlus#159.
The problem is the plugin's module name is serialized without a file extension. N++ fails to locate the module on disk, so never calls NppMarkdownPanel.MarkdownPanelController.TogglePanelVisible() when starting up.
See what happens when the file extension is written to config.xml as the TogglePanelVisible method should be doing.
Click Toggle Markdown Panel and leave the panel showing
Quit Notepad++
Open %AppData%\Notepad++\config.xml (if you have a system-wide installation), or the config.xml inside your portable installation
Notice that NppMarkdownPanel.Main.ModuleName is the value of the pluginName attribute, e.g.,
A forum user asked a while ago why N++'s built-in Docking Manager never reloads the MarkdownViewer++ panel when the application starts. This goes for NppMarkdownPanel as well, and for the same reason, so I'm cross-posting nea/MarkdownViewerPlusPlus#159.
The problem is the plugin's module name is serialized without a file extension. N++ fails to locate the module on disk, so never calls
NppMarkdownPanel.MarkdownPanelController.TogglePanelVisible()
when starting up.See what happens when the file extension is written to
config.xml
as theTogglePanelVisible
method should be doing.Toggle Markdown Panel
and leave the panel showing%AppData%\Notepad++\config.xml
(if you have a system-wide installation), or theconfig.xml
inside your portable installationNppMarkdownPanel.Main.ModuleName
is the value of thepluginName
attribute, e.g.,pluginName="NppMarkdownPanel.dll"
, i.e., append the module's file extension; make sureisVisible
remains"yes"
A tiny patch is all that's needed to make this the default behaviour:
The text was updated successfully, but these errors were encountered: