Notepad3: Recent builds not reading schemes custom file extensions from the ini file

[jupester]

I tried upgrading to a recent version of the NP3 betas, and found that suddenly none of my schemes custom file extensions are recognized from the ini file anymore, I went back through the builds and eventually narrowed the last working build down to 915.1 all subsequent builds won't recognize custom file extensions from the ini file.

[RaiKoHoff]

This is related to new DarkMode feature and the required changed Scheme handling - need to debug the behavior in deeper detail ...

[RaiKoHoff]

@jupester : Does it makes sense to maintain the lexer-file-extensions settings in each scheme file or does it makes more sense to maintain the lexer-file-extensions settings only in the standard .ini-file ?

[jupester]

To me it makes more sense to only have them in the main ini file, I previously raised this with you here:
https://github.com/rizonesoft/Notepad3/issues/2262#issuecomment-626154065

[RaiKoHoff]

Hi @jupester , thank you for reporting and sorry for this regrassion caused by new DarkMode feature, hope this version fixes this.
(There might be more regressions around this themes/schemes area - it is a beta).

Feel free to test the "BETA/RC" version "Notepad3Portable_5.20.927.1_beta.paf" or higher, see below or issue #1129.

• Notepad3Portable_5.20.927.1_beta.paf.exe.7z

"Notepad3Portable BETA/RC paf" version can be used with or without ".7z" extension.
To update "Notepad3 Setup" version with the latest features/fixes from the "BETA/RC" version, see issue #1105.

Comments and suggestions are welcome... 😃

[jupester]

Tried the new build, everything looks good, thanks for another quick resolution.

edit: Just noticed your note, no worries, no need for apologies, I totally understand that I am using betas, and regressions can occur, keep up the good work.