Free Upgrade to 6.0.4 (version 6 users only)
Users of version 6 (licensed, unlocked versions only) can now download a free upgrade to Family Historian 6.0.4.
This upgrade will only work if you already have a licensed copy of version 6 installed. It will not work with earlier versions, or trial, demo or starter editions. Users of earlier versions who wish to upgrade can buy an upgrade to version 6 – see the Store page. To find out which version you have, run Family Historian and click on “About Family Historian” on the Help menu.
6.0.4 ENHANCEMENTS AND BUG FIXES
+ TMG Import Enhancements
- Custom source elements are now correctly labelled in Source record notes.
- Trailing spaces are now removed from Source titles on import.
- Although not directly related to TMG Import, some of the other bug fixes in this release (see below) are likely to be of benefit to TMG users.
+ Report Enhancements and Bug Fixes
- Text from one column (especially long dates) could sometimes overlap another column, in the Individual Summary report and others. This has now been fixed.
- Extra commas in place names are now automatically ‘tidied’ in the Individual Summary report and the Family Group sheet and others.
- There is now, by default, a gap of 0.15″ between all columns in reports that lay out text in columns (e.g. both the Individual Summary report and the Family Group sheet do this in some sections). This gap is configurable in the Page Layout tab of Report options (see the ‘Column Indent’ box).
+ Sundry Other Enhancements and Bug Fixes
- Fixed occasional sizing problem with unusually-shaped pictures in generated websites.
- Previously, if you took an option to ‘go to’ a record in the Records Window, where the current filter settings caused the record to be hidden, nothing would happen. Now the filter is automatically cleared so that the record can be selected.
- Adding the principal in an event (or attribute) as a witness to that same event or attribute, is valid, and sometimes useful. However, previously if you added a principal within a Family fact as a witness to that fact (e.g. if you added the man in a marriage as a witness with role of ‘Groom’), you would get an unwanted extra line in the Facts tab of the Property Box for this, and also an unwanted extra line in the relevant sections of narrative reports. This has been fixed. The extra lines no longer appear. Also, if you select the principal in the Witnesses window, the ‘Go To Witness’ option will be greyed, and the Witness sentence field will display a message to say, in effect, that witness sentences are not applicable to principals (principals get Principal Sentences).
- Previously when custom Family facts are displayed in the Facts tab of the Property Box, the name of the other partner in the family record is displayed in brackets after the descriptive text, preceded by ‘marr.’ for ‘marriage’. Now it only does this if the couple have a marriage event. If they don’t, ‘with’ is used instead.
- If you opened the ‘External File Links’ tool (accessible from the Tools menu) and closed it by clicking the OK button, all Media records would be marked as having been modified, and their last-updated date would be updated accordingly. Now this only happens for a Media record if it has in fact been changed.
6.0.3 ENHANCEMENTS AND BUG FIXES
+ TMG Import Enhancements
- Source elements are now imported as labelled values within source record notes.
- Previously if an Individual event had 2 principals this was handled by creating a separate event for each Individual. This had various disadvantages. Now a better solution has been adopted which is to create only one event and to add the second Individual as a ‘witness’ to the event.
+ Narrative Report Enhancements and Bug Fixes
- Numeric references to source citations were not always handled correctly if the text they should have been attached to was near the end of a line. The numbers could become detached from the text, and even overlay other text on the same line. Both problems have now been fixed.
- The layout of text has now been improved and made more accurate, especially when numeric references to source citations are involved.
- Previously, spaces were sometimes incorrectly added in front of commas and full-stops. Now fixed.
- If you put the formatting codes <br> or <para> (line-break and new paragraph respectively) at the start of a sentence template, the first letter of the sentence was not being capitalised correctly. Now fixed.
- If you put <br> or <para> at the end of a sentence template, any numeric references to source citations attached to the text were ‘wrapped’ to the next line. Now fixed.
- The formatting codes <br> and <para> were not handled consistently in web pages, or if you saved the report in word-processing format (RTF). Both problems now fixed.
- When generating sentences for narrative reports, approximate dates could be rendered with both ‘in’ and ‘circa’ – e.g. ‘in circa 1984′. There is now an option to avoid using ‘circa’ at all (see above), but if you opt to use ‘circa’ it will no longer be prefixed by ‘in’ or ‘on’.
- The Sentence field in the Fact tab of the Property Box could appear to be blank if you put at the start of a line – because the text could then be moved down 2 lines and effectively scrolled out of view. To get round this problem, no line-breaks are shown in the Sentence field. Instead, a large black dot is displayed where line-breaks will appear in the narrative reports.
+ Sundry Enhancements
- It is now possible to choose between the new style of text for approximate dates (using ‘c.’ and ‘circa’) or the version 5 style (using ‘(approx.)’ etc.). The option is in the General tab of Preferences.
- Within the Property Box and the Automatic Source Citation pane, you can quickly select an accent character by pressing-and-holding any key to see a popup window with a choice of accents for that character. Now this also works in the Find window and the Find/Replace window.
- When using drag-and-drop, you can append a value to a field, by dragging to the right of the text. However, previously, this only worked with multiline fields. It now works with single line fields also.
- When importing a family tree file into a new project, Family Historian offers a proposed name for the new project, based on the file name. Previously the proposed name might not be allowed if there is already a project with that name. Now Family Historian adds a number in brackets on the end, in this situation, to ensure that the proposed name is unique. The name is of course editable in any case.
+ Sundry Bug Fixes
- Opening and closing the ‘Show Media’ window for a fact could cause a delayed crash. Now fixed.
- In Windows 8.1, Family Historian did not start if the text size was set to 200%. Now fixed.
- In some contexts, the word ‘circa’ was used as the displayed text for estimated and calculated dates, when it was only intended that it should used with approximate dates (if at all – see above). Now fixed.
- Previously, pressing the Escape key when viewing a floating source citation window caused it to be hidden but not closed. Now it is closed.
- Incorrect menu text for ‘Paste Copied Picture’ has been corrected.
- Doing a Search/Replace with a ‘/’ character in the search string was not always handled correctly. Now fixed.
- If you make someone the file root when they are listed as a child in the Focus Window, their icon should change to a small blue arrow pointing down. That did not happen previously, but now does.
- Previously it was possible to make Family Historian crash if you clicked the ‘>’ button in the Columns tab of the Query Window, when viewing a result set that had been created using the ‘Find’ command (i.e. using the option to display results in the Query Window). This has been fixed.
+ Power-User Enhancements
- The Plugin Editor only displayed 6 significant digits for some numerical values which sometimes meant inappropriate truncation. It now displays all digits before the decimal point and up to 6 after it.
- The function fhSetValueAsLink can now be used, with a link to a Place record, as an alternative way of setting the value of a Place field.
- There is now a quick and convenient way of finding the tag (data reference) for any field. Open the Query Window and select any query of the record type of the field in question. You can now opt to display the data reference for each selected field/data item, instead of its description (or as well as its description) in the Columns tab of the Query Window. Click on the down arrow in the bottom-left corner of the window. A popup menu appears with options relating to the display of data references.
6.0.2 ENHANCEMENTS AND BUG FIXES
+ TMG Import Enhancements
- When you import a TMG project, there is now a new ‘TMG Import Options’ page. You can simply accept the defaults, or you can opt to use ‘Custom Options’. All custom options are explained in the Help (just press the Help button).
- A date specified as ‘before’ a given date, was being imported without the ‘before’ and there were similar problems with other date ranges. Fixed.
- Memos for events are now imported (witness memos have been imported since 6.0.1).
- Note tags were imported but the note text was lost. Now fixed.
- Both the description and caption for exhibits are now imported.
- Where the principal for a TMG tag has a role other than ‘Principal’ (e.g. ‘Head of Household’ in a census), the default option is now that the principal is now added as a witness to the event, with the specified role (can be overridden in custom options).
- FH makes a distinction which TMG does not make, between events and attributes. For example, in FH, ‘Occupation’ is an ‘attribute’ where in TMG it is just another ‘event’. Attributes, in FH, have all the same fields as events, plus one additional one: a Value field. For example, the value for Occupation might be ‘farmer’. In TMG there is no Value field – just a Memo field. Whereas for ordinary events, the Memo field is simply moved to the FH Note field, for attributes, things are less straightforward. In these cases, the Memo must be divided or shared between the attribute’s Value field and its Note field. New custom options specify in what way this should be done. The default policy is that the first sentence of the Memo is moved to the attribute value, and the entire memo is moved to the Note, unless the Note would as a result be an exact duplicate of the Value.
+ Enhancements to the Internet Search Tool
- The Internet Search Tool has been updated with the latest search templates.
- There is a new button on the Internet Search Tool, called ‘Check for Search Tool Updates’. Clicking this button will look for updates to search templates, and optionally install them, if found.
- The Internet Search Tool now automatically updates its search values when you click on a person in the main program. So, for example, if the Internet Search tool is open with ‘FindMyPast’ selected, you can simply click on a person in the Focus Window (or elsewhere) and then click on the ‘Search Now’ button to search for the records for them.
+ Sundry Enhancements and Bug Fixes
- Map references did not work if your preferred decimal point symbol (set in ‘Region settings’ in the Control Pane) was a comma, or at least, not a dot. Using a comma as a decimal point symbol is normal in Germany and other countries. Map references now work correctly whatever your preferred decimal point symbol – but you still have to use a dot as decimal point symbol within map references.
- On the Fact tab, you can now optionally display surnames for relatives referenced in Timeline events. This is specified in ‘Timeline Facts’, which is accessible both from the Fact Tab, and from the General tab of Preferences.
- When exporting a GEDCOM file, there is now an option to exclude Place records.
- The chosen option for ‘Autogenerate Keywords’ in Preferences was not preserved from one session to another. Now fixed.
- Clicking on a marker in the Map window did nothing if you were in standalone GEDCOM mode. Now fixed.
- Workspace preferences were not handled correctly if you opened multiple instances of the same type of workspace. For example, if you opened multiple Map windows, your preferred positioning of the Property Box might not be handled correctly when you switched between them. Now fixed.
- There is a new Export menu command to allow the standard fact set to be exported. When you re-import it, however, you must import it as a new custom fact set, and rename it.
- It was previously possible to edit a place while in the process of selecting it for a merge. Doing so caused FH to crash. It is no longer possible to edit the place name while you are in the process of merging.
- New commands have been added to the Fact Sets dialog. You can now delete, rename and clone custom fact sets. You can also clone or reset the standard fact set. To view the Fact Sets dialog, click on ‘Tools’, then ‘Fact Types’, and then click on the ‘Fact Sets’ button. The new commands are described in the Help.
- If you immediately closed the Property Box after making a change to a field, the change was not always recorded. Now fixed.
- Added an option to create new named lists to the right-click menu in the Named List pane (top panel) in the Record Window.
+ Power-User Enhancements
- The ‘ContainsText’ function did not handle place names correctly. Now fixed.
- When FH generates an exception report, it now writes a ‘BOM’ to the start of the file, which means that more text editors are likely to correctly identify the text encoding.
- The ‘TextPart’ function had 2 problems: it could not be called from a plugin using the function fhCallBuiltInFunction, and it could cause a crash with some place fields, when used in queries. Both problems now fixed.
- The Accent Popup window is now always disabled in the Plugin Editor.
- In the Row tab of the Query window, if you entered a data reference to a place field (i.e. with no chevron on the end – e.g. %FACT.PLAC%), the ‘Operator’ field would wrongly include ‘is’ (for record-matching), and would wrongly exclude ‘is null’. Both now fixed.
6.0.1 ENHANCEMENTS AND BUG FIXES
+ TMG Import Enhancements
- Import of The Master Genealogist files previously crashed if the file contained Witness memos. Fixed.
+ Sundry Enhancements and Bug Fixes
- Time slider did not display correctly if the Windows Classic Theme was chosen in Vista or Windows 7. Now fixed.
- Internet Data Matching now uses SSL to connect to MyHeritage.
- Text box font details in chart files created in version 5, were not loaded correctly in version 6. Problem could also affect books. Now fixed.
- Some projects could take a very long time to load – even to the point that the application appeared to hang. Problem was caused by an inefficient method of identifying ancestors of the File Root, in the Focus Window. Could also mean that the Focus Window could be slow to display. Now fixed.
If you are looking for upgrades for earlier versions please see the download archive. See Understanding Family Historian Version Numbers for an explanation of how Family Historian version numbers work.