+ to avoid unexpected "accelerated word navigation" behavior,
space-char extension is restricted to 7-bit ASCII char set (ignoring specified non-7-bit-ASCII chars).
- 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
