Implement a mechanism of updating default toolbar configuration according to program changes. In other words, determine default values of ToolbarButtons from git history (including the original value of Notepad2 4.2.25), record them into a static array and test current ToolbarButtons value: if it's part of that array, clear it (i.e. set ToolbarButtons to current default value), else keep it. To keep the array short it's possible to exclude short-lived TOolbarButtons values (present in code for several commits/days only).
This will allow users of old versions who didn't customize the toolbar have the new set of buttons (including split view and show outline) when they upgrade to latest Notepad 2e.
cshnik
commented
1 year ago
Implement a mechanism of updating default toolbar configuration according to program changes. In other words, determine default values of
ToolbarButtonsfrom git history (including the original value of Notepad2 4.2.25), record them into a static array and test currentToolbarButtonsvalue: if it's part of that array, clear it (i.e. setToolbarButtonsto current default value), else keep it. To keep the array short it's possible to exclude short-livedTOolbarButtonsvalues (present in code for several commits/days only).This will allow users of old versions who didn't customize the toolbar have the new set of buttons (including split view and show outline) when they upgrade to latest Notepad 2e.