* New Patch for FH released

[admin]

Calico Pie have just released a minor upgrade of Family Historian: version 2.3.5. This is a 'patch' - i.e. a bug fix release).  The upgrade can be downloaded from www.family-historian.co.uk, or from the downloads section on this site.
The bugs fixed are:

• 1. The Descendant Outline report, using generation level numbering, was numbering generations as 1, 3, 5 etc. This has now been fixed.
• 2. In the Descendant Outline report, the option to include (or exclude) the names of spouses' parents, had no effect. They were always included regardless. This has now been fixed.
• 3. When loading a file into Family Historian that was not created by Family Historian, you could sometimes get an incorrect message asking you if you wanted to reload the file, even while the file loading was still in process. This message no longer appears.
• 4. If you created custom events and attributes that had names which contained accent characters, the expressions representing these events and attributes (in queries etc) could work differently in different countries, which might mean that a query created in one country would not work if sent to someone in another country. This problem has now been fixed, and all 'location-dependence' has been removed. However, if you have any custom attributes or events which have names that contain accent characters, and if you have custom queries that refer to them, you may have to recreate the relevant expressions in these queries.
• 5. The maximum size of a text scheme in a diagram was too small. This has been increased five-fold to allow for larger text schemes.

Finally, although not strictly a bug, there was an issue about how Emigration and Immigration was handled.  There was a confusion about whether the 'place' was the place from which, or to which, the person had emigrated or immigrated. The way that F.H. handled this was correct (i.e. correct to the standard for shared genealogy data - GEDCOM): the Place for an emigration event was (and still is) the place FROM which a person had emigrated, and the place for an Immigration event was and is the place TO which a person had immigrated.  However, previously this wasn't obvious when you entered the data.  Also, several people wanted to be able to get narrative reports to say that, for example, 'X had emigrated to Canada' and there was no way to do this (you had to put up with 'X had immigrated to Canada' which sometimes didn't seem right).  To get round the problem, we have now added a 2nd place field for Emigration and Immigration events; so that for both Emigration and Immigration, you can now specify both the 'From' and the 'To' place (and its now clearer which is which, because the new place field is labelled simply 'To' or 'From' as appropriate).

These new fields are optional.  You can continue to use Emigration and Immigration events exactly as before, and ignore the new place fields, if you wish to.

Given that you now have both a From and a To place for Emigration, you might ask - why do you need an Immigration event too?  Can't you just use the Emigration event and ignore Immigration (or vice versa)?  The answer is that yes you can.  That would be quite a reasonable thing to do.  If you do just use the one though, be aware that if you move your data to another genealogy program it will almost certainly not recognise the Emigration event's TO place field, or the Immigration event's FROM place field; so that bit of information would probably be lost in the transfer.  If you are concerned about that issue you might wish to consider repeating the extra place field information in the Note (perhaps as Hidden text, in double square brackets like: [[To: Canada]]).  Or you could have both an Emigration and an Immigration event with duplicated data, but hide one of them in reports.

Finally, thank you very much to the beta-testers who who tested the upgrade for us.

Simon Orde List
Administrator & Family Historian designer