- correct entry is 'SciDirectWriteTech', must by manually edited
+ add possibility of override SciDirectWriteTech Settings (general section),
by resolution specific specialization (using general settings if not defined)
+ add: toggle option for accelerated word navigation (Ctrl+LEFT/RIGHT)
according to issue #27 (https://github.com/rizonesoft/Notepad3/issues/27)
- [Settings2] parameter "ExtendedWhiteSpaceChars=" defines a
set of chars to be ignored (handled as whitespaces) to find the next beginning of a word
if "Accelerated word navigation" is switched ON
and put some of the "hidden" shortcuts into NP3's menu tree.
- couldn't reproduce the "reload as UTF-8 not work bug" in NP3 (?) - so didn't merge the related change.
(if someone can reproduce it, please tell me)
+ I "guard" the shortcut for direct editing the NP3's .ini-file (Ctrl+F7) by disabling "Save Settings Now (F7)" and "Save Settings on Exit" - Flag
as long as I edit the settings file itself.
(Example not disabling this: Editing the .ini-file while "Save Settings on Exit"-Flag is checked,
leaving NP3 would override the just edited .ini-file with "old" NP3 settings ...)
+ option: build-time: treat warning as error (build fails)
+ cleanups reported by CppCheck v.1.79 (except issue: 'variableScope')
+ remove _CRT_SECURE_NO_WARNINGS to see security warnings for deprecated functions;
+ remove macro-definition for BOOKMARK_EDITION (bookmarks are fixed component of NP3 now)
(code has not been excaped by this MACRO consistently)
- using Linker generated manifests (knows dependencies)
- activate VS2017's postprocessing manifest-tool to merge manifest with
Version.exe's .manifest.conf part (re-embedding assembled manifest)
- by the way: Version.exe (Release/Win32) should only patch the items in
<assemblyIdentity /> node of .manifest.conf and not re-create the complete manifest wiith dependencies
(it works fine yet, but, if the Linker change dependencies, this will lead to merge conflicts)
- switching DPI awarenes to 'false', cause only MFC Application can be made DPI aware
(setting 'true' for non MFC Applications will end up in blurry effects on scaled desktops [MS doc])
- Tip: the embedded manifest resource can be checked by:
i) load the .exe via file open dialog into VS2017
ii) or using Sysinternal's > sigcheck.exe -a -m Notepad3.exe
~ maybe it is time to change to Platform Toolset "Visual Studio 2017 - Windows XP (v141_xp)" ?
- add existing recoding accelerator keys (Ctrl+Alt+F & Ctrl+Shift+A)
to "Recode" menue (func: reload file forcing this encoding type)
- add version info for used Scintilla library
~ VERSION_SCIVERSION should be set by Version.exe (version patcher)
and can be picked from provided scintilla\version.txt
- some code-cleanup (cleancode-developer pathfinder rule)
while trying to trace down notepad2-mod issue #121
(i am able to reproduce, but didn't find the reason (yet))
- fix exception - reported in notepad2-mod pull request (Crash fixing. #172), which has been rejected there,
but I was able to reproduce it in VS2017 debug mode (initial defaults for exception handling).
(https://github.com/XhmikosR/notepad2-mod/pull/172)
- incorporate changes from notepad2-mod from v.4.2.25.995 to v.4.2.25.998
(one fix, the other changes we have done before already)
- Change shortcuts for the following actions:
(-) Toggle Transparent Mode: moved from Ctrl+0 to Ctrl+Numpad_*
(x) Reset Zoom: Ctrl+/ change to Ctrl+0 ($v_5.0.26)
Additional Accelerator Keys, as suggested by (https://github.com/XhmikosR/notepad2-mod/pull/197)
(+) Toggle Line Comment : in addition to Ctrl+Q add Ctrl+/ with same functionality
(+) Do Stream Comment : in addition to Ctrl+Shift+Q add Ctrl+Shift+/ with same functionality
believing new shortcuts are more convenient and more widely used, aren't they?
- consistent encoding <> code-page handling (including Scintilla's code-page settings)
- Scintilla issue regarding notepad2-mod issie #173 (see https://github.com/XhmikosR/notepad2-mod/pull/193)
- allow arbitrary conversion between encodings (even it it does not make sense in any case)
(instead of doing silently nothing but changing encoding info on status bar)
- using Scintilla UTF8 code-page internally for most encodings,
solves some encoding/code-page problems, the behaviour slightly changes:
+ if DefaultEncoding is not set (or set to DefaultEncoding = -1),
initial encoding is set to current system's code-page, e.g. Windows-1252
Scintilla's internal UTF8 code-page is used for edit box,
that means copy/paste from clipboard may show characters which are
not valid in this char-set of the selected code-page.
Trying to save a file with this invalid UTF8 chars will result in conversion dialog:
("... encoding from ANSI to non-ANSI (and vice versa) may replace unsupported text with default characters ...")
+ if DeaultEncoding = 0 (ANSI):
a) if LoadASCIIasUTF8 = 0 (FALSE), Scintilla's internal ANSI code-page is used for edit box
that means copy/paste from clipboard may convert chars to ANSI ()
b) if LoadASCIIasUTF8 = 1 (TRUE), Scintilla's internal UTF8 code-page is used for edit box
that means the universal UTF8 encoding is used
+ if DeaultEncoding = nnn (corresponding to some ANSI code-page encoding):
same as if DefaultEncoding is set to corresponding code-page (see section "DefaultEncoding is not set")
