* Spellcheck / Ignore Spelling option

[jbtapscott]

Not sure if I'm missing a setting here or not, but it seems to me that the "spellcheck" dictionary is being reset each time a new version of FH is installed (I'm on 7.07). I don't make great use of the process but in various Note fields I know I have used the "Ignore Spelling" option for a number of highlighted words since installing 7.0 (including my own surname) but when I went to the Preferences / Notes / Custom Dictionary / Edit option today there were only two words listed - both of which I had added yesterday.

Unless somebody can point me to some install option or similar, I'll get this flagged up with CP.

[LornaCraig]

Yes, I can confirm that. I have never noticed it before so I wonder if it has only happened with the latest upgrade to 7.0.7?

[jbtapscott]

Thanks Lorna. I had a feeling it was happening in earlier versions, but as it wasn't something I was overly using I didn't really check in to it. I'll flag it up with CP.

[jbtapscott]

CP (Martin) have responded "Thank you for reporting that. We have confirmed that you are quite right. We will fix this in the next upgrade. I have made a note to contact you when the update is available. "

[Mark1834]

Thanks for reporting that. I can pass on a tip that might prove useful in these circumstances.

Prior to upgrading FH, I always take a complete copy of the FH ProgramData folder via a shortcut to a batch file on my desktop. I don't have to think about which options I am saving, it just does everything with one click.

FH saves its custom dictionary in the Spellcheck folder, and while CP give it a custom name (Custom.fhdic), it appears to be a simple plain text file. If something appears to have been blown away by an update, there is a good chance you can recover a copy from your backup and restore it back to the live folder. For users who are comfortable manipulating files directly, it's always worth getting familiar with where and how FH saves its options so you can recover from such whoopsies even if you don't use the various plugins available or it is something that the plugin does not copy. There is a good overview at Understanding the Scope of Features.

[Gowermick]

In a similar vein, I lost some custom settings too when I updated.
In the ‘Add Fact…’ in the property box, I had previously added the ‘Probate’ fact to the quick list of dropdown facts, but this disappeared after an update. I had to add it back to the list later.
A minor, insignificant omission, but one does wonder what other custom settings got lost along the way!

[tatewise]

Unfortunately, updated versions of FH, including the v7.0 bug fix subversions, don't always preserve all custom settings.
There have been several omissions reported with spellcheck being the latest.
It seems that the general requirement to preserve settings is not always part of the global CP design & test strategy.
So updated features or new features sometimes overlook that requirement. Moan over!

[jbtapscott]

Thanks Mark - should have thought of my backup as well!. That Program Data folder is auto backed up to the "cloud" each day with my Documents, Photos, etc., but I might well have a look at a separate batch file that I can run prior to installing updates in future.

[tatewise]

Don't forget the Backup and Restore Family Historian Settings plugin is an alternative.

[jbtapscott]

Thanks Mike - I use that as well but only on a weekly basis (if I remember!)

[Mark1834]

I see them as complementary rather than alternatives. The plugin gives more fine control and is a good option (perhaps even the only option) for syncing all settings across different PCs, but I find the batch file approach much quicker and easier to run for recovery to the same PC. It depends on how willing users are to roll up their sleeves and get to grips with the detailed FH file structure.

[jbtapscott]

An update re the Spellcheck problem. I received an email overnight from CP advising that the issue had been fixed and giving me an option to download the pre-release version 7.0.8 . I have done that and can confirm that the issue has been resolved - viz. installing the update did not reset the custom dictionary to blank.