#16 Unsaved changed code page

[Yearling]

The problem (unsaved configuration) described in ticket 14 still exists (v. 1.7.2.567) - when I open csv file (default code page is CP 65001 Unicode UTF8), in configuration on "Read Settings" tab I switch code page on CP 1250, after close Setting windows is file reopened with setted code page CP1250, but when I this file close and open next file, that file is opened in CP65001 UTF8 again (in Setting is the first item in the list - CP65001 UTF8 again) - so the changed setting code pagewere not saved anywhere.
I have checked configuration file setting.json in %AppData%\Roaming\CSVQuickViewer\ folder, but there is not any saved section "CodePage".

[Raphael Noeldner]

Every time a file is opened the application will determine the code page unless "Determine Code Pages" is unchecked.
The issue is that the selected code page is not persisted and therefor not used the next time a file is opened without detecting a code page.

I now realize that I have never used the application without code page detection, the code page detection is very good thanks to the nuget package UTF.Unknown and I get files with all different encodings so I never had the need to change these code page or be persicptive about them.

I am glad to hear the reload is triggered properly and will persist the selected code page for the next use.

In the mean time you could save the settings for a file, under "Behaviour and Warnings" is an option to "Persist Setting for File".
If checked it will create a small information file, opening the file again it would not inspect anything but use the setting from the last open.

[Raphael Noeldner]

Changes are now persistent for all settings that are possibly determined by inspection.

This includes Code Page, BOM, Delimiter, Skip Rows, Qualifier/Quoting, Line Comment, Header and Escape Seqence