Use tabContextMenu_example.xml for the customization:
1. rename to tabContextMenu.xml
2. modify it
3. copy it beside notepad++.exe or to %APPDATA%\Notepad++\ according to your Notepad++ conf
4. relaunch Notepad++
Note for the localization:
1. You have to use the newest localization file (or modify your existing localization file with the newest english.xml).
2. The customized sub-menu entry cannot be translated. User can use his/her native language as value of attribute "FolderName" in tabContextMenu.xml file.
3. User can always add any command beyond the default commands in tabContextMenu.xml file. But such command won't be translated.
Fix#12170, close#12576
Now if the Notepad++ will have an unsaved data and is still running at the OS restart/shutdown, there will be one universal messagebox "Windows session is about to be terminated but you have some data unsaved. Do you want to exit Notepad++ now?".
When Notepad++ backup mode is ON, answer:
- YES ... Notepad++ simply quits (Notepad++ backup engine silently handles all the stuff needed)
- NO ... Notepad++ stays running, user is on his/her own
When Notepad++ backup mode is OFF, answer:
- YES ... Notepad++ behaves identically as in the case of the usual Notepad++ IDM_FILE_EXIT or WM_CLOSE messages (save dlgs appears etc., it depends on the current user Notepad++ settings)
- NO ... Notepad++ stays running, user is on his/her own
Fix v847
1. Add "Follow Windows dark/light mode".
2. Remember user's toolbar, tabbar and theme choices for dark mode and light mode separately.
3. Add 2 hidden options for applying tab background color from themes (for both dark mode and light mode).
Fix#9183, fix#9992, fix#10153, fix#10239, fix#10544, fix#10644, fix#11867, fix#10239, close#12466
This fixes both the long standing problem with the emptying of the session.xml file by forced Windows Update restart/shutdown and some potential Notepad++ crashes caused by possible main Notepad++ window blocking at exit.
Two main changes to the original design:
- WM_QUERYENDSESSION is not used anymore for the tidy-up ops and it always quickly returns TRUE/FALSE to the system as it should.
- there is now a safe-guard flag for the session.xml saving at N++ exit, which prevents otherwise possible incorrect overwriting in case of multiple "endsession" messages.
Fix#9850, fix#12389, close#12388
ArkadiuszMichalski