Family Historian Version 6.2.7

Features

New in 6.2.7 (May 2018)

  • Product registration has been modified to conform to new EU regulation (GDPR).

New in 6.2.6 (Jan 2018)

  • Access to the FindMyPast hinting service has been improved and made more robust.
  • The thumbnail cache (ThumbCache.dat) is now excluded from backups. There is no need for it to be backed-up as it is re-generated on demand; and without it, backups are faster and smaller.
  • Family Historian no longer makes any assumptions about how Ancestry and Family Tree Maker handle line-breaks in long text such as Notes when importing their GEDCOM files (Family Tree Maker changed the way it handles them recently).
  • When importing from Family Tree Maker, the information about which picture is the preferred picture, is now included in the import.
  • Future-proofing and robustness features have been added.
  • Some minor bugs have been fixed.
  • Emulation for the Mac and Linux has been improved (to enable this, click Tools and then Preferences; then click the Advanced button on the General tab, and tick Emulator Compatibility Mode). These enhancements remove many of the previous limitations of running Family Historian under an emulator on the Mac or Linux. However there are still a few known limitations:
    • a) PDF support is still not enabled;
    • b) Fan Charts still don’t work;
    • c) Some form windows may display with caption bar only, the first time you open them. If you close and re-open them, thereafter they should be OK;
    • d) Links to FindMyPast hints may not work if you use the option to display the linked page in the Web Search Window. You are recommended to use an External Web Browser instead (this is a Tools > Preferences > Internet Data Matches option).

New in 6.2.5 (May 2017)

  • Adds new functionality to ensure the continued operation of the automatic geocoding feature, following changes by service providers. Also adds future-proofing and robustness improvements. See Map Search and Geocoding.
  • Adds a new option (checked by default) to automatically save changes on close, without prompting, if autosave is enabled.
  • Improves preservation of record ids on import. Previously, when a GEDCOM file is imported, if a record of one type had to be renumbered, all records would be renumbered. Now record ids are preserved as much as possible, and renumbering only happens for those record types where it is needed.

New in 6.2.4 (Mar 2017)

  • Adds new functionality to ensure the continued operation of the automatic geocoding feature, following changes by service providers. See Map Search and Geocoding.
  • Adds improved support for PDF creation.
  • Fixes problems where (usually following an import from another program) picture types were not being identified correctly.
  • Adds an alternative mechanism for opening the Accent popup window which can be chosen in Preferences (General tab). The default way to open the Accent popup window is to press-and-hold a letter key when editing a note. For example, if you press-and-hold the ‘e’ key, a popup window will appear showing accents for the letter ‘e’. The alternative method (if enabled) is to press-and-hold the Insert key and then press the letter key. You can enable the alternative method in the General tab of Preferences.

New in 6.2.3 (Feb 2017)

Note: A planned 6.2.3 release was replaced by 6.2.4 when 6.2.3 was discovered to include a bug which prevented a small number of users from opening their projects. It is thought that 6.2.4 fixed a rare problem related to embedded OLE objects in Gedcom files, which stopped such a file loading.

6.2.3 also fixed a number of unspecified bugs, but only the following have been detected.

  • Merge/Compare File crashed with an obscure particular combination of near matches. This is now fixed.
  • FIXME

New in 6.2.2 (Jun 2016)

  • Adds faster application startup.
  • Improves auto-completion of place names.
    This relates to FHUG Forum thread autofill places.
  • Fixes a number of minor issues.

New in 6.2.1 (Jun 2016)

  • Fixes issues with checking for updates.
    This is possibly in response to [FHU] Mailing List thread FH slow to start and modifies the Check for Updates, which may have impacted users on offline computers.
  • Fixes problem with importing GEDCOM files with extremely long lines.
  • Fixes a number of minor issues.

New in 6.2.0 (Apr 2016)

  • Improves appearance of hint popups, in the Focus Window.

New in 6.1.4 (Feb 2016)

Improved GEDCOM Import, especially from Family Tree Maker and Ancestry GEDCOM files

  • A new feature called Smart GEDCOM Loading has been added, which delivers big improvements in GEDCOM imports – especially from Family Tree Maker and Ancestry GEDCOM files. The same feature can even be used to recover hidden data in existing Family Historian projects that were previously created by imports from Family Tree Maker or Ancestry (click Recover Uncategorised Data on the Uncategorised Data submenu of the Tools menu).

Improved Direct Import from The Master Genealogist

  • A number of enhancements have been made to the handling of names on import. Prefixes, suffixes, and titles are all now handled appropriately. The Title field is treated as another prefix. The preSurname field, if used, is inserted before the surname. The Other Name field, if used, is moved to the Family Historian Nickname field. Surnames are no longer capitalised on load. Name parts which begin with a hyphen are ignored. Imported spouses, children and siblings are automatically put in the correct chronological order. A bug which sometimes prevented the abbreviation for a repository from being included in a TMG import, has now been fixed. There was a problem with the import of ‘internal text’ files under the ‘exhibit’ tab. Only the first 300 words, approximately, of each text file came across. This also has been fixed. Creating new fact definitions for imported TMG facts could be problematic if the fact name contained certain non-alphabetic and non-numeric characters. This has also been fixed.

Improved Direct Import from Genbox

  • Witnesses to events are now imported as witnesses, and are not simply recorded as witnesses in a Note field. Source citations for witnesses are now also imported (source citations for witnesses can be viewed in the Source pane when you select a witness in the Witnesses window). Imported spouses, children and siblings are automatically put in the correct chronological order.

Add Source Citations for Parent-Child Relationships as well as Spouse Relationships

  • You can now add source citations for all relationships, including parent-child relationships. To add a source citation for person Y as father of person X, use the Witnesses window for X’s birth event, to add person Y with role of ‘father’. You can then add source citations for Y in this role, with respect to X’s birth. A new sentence template code is used to prevent unwanted sentences being generated for this, in narrative reports. You can use the same technique to add source citations for adoptive parents. Adding a source citation for a spouse relationship has always been possible, by simply adding source citations for their marriage.

‘No principal’ and ‘Multi-principal’ Events

  • Most events, such as birth and death, have one person who is clearly the principal participant in the event. A few, like marriage, have two principals. But sometimes you may want to create an event which is shared between several people, where none of them really have a special claim to be the principal. You might say that they all are principals, or that none of them are. Fact types can now be defined so that they behave for almost all purposes, as if they have no principal (or as if they have multiple principals – it amounts to the same thing). For example, if five people lived together, you can record this with a single residence event which all five share. To do this, you just use the Witnesses window to add all five to the same event as witnesses (a ‘witness’ in this sense just means a non-principal participant) with role Resident. One of them, it is true, has to also nominally be recorded as the principal. But all five will be treated identically in reports, and almost identically in all other contexts (such as the Facts tab of the Property Box). So for all practical purposes, the event can be viewed as a no-principal, or as a multi-principal, event.

Improved Handling of Source Citation Media

  • The Media Viewer window (previously known as the Show Media dialog) had been used previously only for displaying media linked to an event. Now it has been enhanced to allow it to also be used to display media associated with a source citation – that is, either media linked to the Source record, or media linked to the citation. You can see at a glance, the number of items in each category and easily switch between them. You can also use the Media Viewer to add media of either type, either by clicking the ‘Add’ button, or by dragging media files onto the window. The Media Viewer is a floating window that does not have to be closed. It displays media for whatever fact or source citation, is selected in the Property Box. So if the Media Viewer is already open, one click on a listed source citation in the yellow Source pane is all it takes to view the source citation’s media, if any. If the Media Viewer isn’t already open, just one additional click is required on a Source pane toolbar button, to open it. Right-click on each thumbnail image displayed in the Media Viewer, to see a convenient dropdown menu of things you do with that media item.
  • The yellow Source pane has also been enhanced so that you can see at glance which source citations have linked media, thanks to a new media icon which displays on the right, for each row in the list of source citations, if the source citation has associated media. A new menu button on the Sources pane toolbar provides yet more options for displaying source citation media. They can be displayed either in the workspace Media Window, or in an external editor/player.
  • As mentioned before, the Media Viewer can also be used to display media linked to an event. This usage has also been improved. For example, you can now optionally include all media for all source citations for the event, if you wish.

Automatically Fix Problems with Missing Pictures

  • Family Historian lets you choose to copy pictures into your project folder, if you wish, or to keep them elsewhere on your hard disk. If you choose the latter option, Family Historian has to maintain links to the pictures held elsewhere. It can easily happen, if files are moved or folders renamed, that the links to them get broken. When that happens, you will see an empty box instead of a picture, for that person, within Family Historian. The same problem can sometimes happen when you import into a new project, if the pictures are not found at the time of the import. Previously, Family Historian provided a powerful tool, Work with External File Links, to help you identify and solve any such problems. That tool is still there, but there is now an additional option, which is to ask Family Historian to automatically find the missing files and repair the broken links for you. The new auto-repair feature will be offered to you as an option, whenever the need for it arises. But you can also access it at any time by clicking on the new Auto Repair Links button, on the Work with External File Links tool (accessible from the Tools menu).

Automatic Snapshots

  • Family Historian can now automatically take and store daily snapshots of your entire data file, so that you can easily revert to an earlier version if you need to (this is in addition to full multi-level undo/redo within each session). By default, only the 8 most recent snaphots are kept, to ensure that space taken by snapshots never becomes excessive (this is configurable in Advanced settings, in Preferences). The new Snapshot Manager allows snapshots to be viewed or deleted – or reverted to. It can be accessed by clicking ‘Revert to Snapshot’ on the ‘Backup/Restore’ submenu of the File menu, or, in the Project Window, by selecting a project and clicking ‘More Tasks’, and then ‘Manage Snapshots’.
  • This feature provides additional security over and above the security offered by backups, but should not be viewed as in any way a substitute for regular backups.

No More Unnecessary Slashes Round Surnames

  • If the surname is the last word in the name, Family Historian will, by default, no longer put slashes round the surname in the Property Box. Gives it a neater look, we think, for no loss of functionality. Use Tools > Preferences > Property Box to alter the setting.

Better and Easier Options for Generating Sentences in Narrative Reports

  • You don’t have to be a power-user (expert) to modify sentence templates for narrative reports. But some of the more powerful and advanced features that Family Historian offers with respect to sentence templates and sentence generation, are likely to be primarily of interest to power-users. That said, the new enhancements simplify things somewhat. The Insert Code button which features in the Fact Definition dialog and in the Edit Role dialog, produces a dropdown menu for inserting template codes into sentence templates. It now has a new menu option for inserting data references, which makes them much easier to insert (‘data references’ are Family Historian’s low-level mechanism for referencing any item of data from almost anywhere). New ‘contextual data references’ now make it much easier to reference everything relating to the participants (principals or witnesses) in events. See the Help – especially the pages for ‘Template Codes’ and ‘Understanding Data References’ – for more details. Both pages have been updated and improved with more examples.

Alternative map types in the Map Window

  • The alternative map type, OSM Roads, had stopped working in the Map Window owing to changes in the way that the service operated. It now works once again.

New Witnessed Events query

  • The new Witnessed Events query lists everyone who has participated in an event in a non-principal role, and gives details of up to 9 instances in which they have done so.

Easier installation of upgrades

  • The Check for Updates functionality has been improved. You will be able to install the latest free update by simply clicking a new Upgrade Now button.

Improved support for companion products

  • Family Historian family tree data is stored in a GEDCOM file. You can now optionally specify that this file should always be saved in UTF-8 format (see Preferences, File Load/Save tab). This greatly increases the likelihood that other applications will be able to load the GEDCOM file, without the need to export it. The default however is still UTF-16 (formally equivalent to UTF-8, but less widely supported by other applications).
  • FH now saves the last-used record id for each record type in the GEDCOM file, which avoids some potential problems that could otherwise arise with certain companion products (such as Clooz).
  • There is a new registry setting: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Calico Pie\Family Historian\2.0\Preferences\Dgm Stats Output File. If you put a full path file name into this setting, FH will save the “Diagram Statistics” to that file, every time you run the “Save Diagram as PDF” functionality. This feature was requested in relation to a companion product used for automatically generating diagrams.

Three standard fact definitions have been updated. Old custom versions can still be accessed.

  • What happens when standard fact definitions are updated? Are custom modifications lost? The answer is that custom modifications to fact definitions (such as changes to sentence templates) are always retained, unless the standard fact definition changes – as it has been for Birth, Adoption and Census in this upgrade. These modifications were made to support some of the features mentioned earlier. But even if your particular modifications are replaced during an upgrade, they are not lost. You will still be able to view and copy your old versions of sentence templates, by clicking on the new Old Versions button which has been added to the Fact Definition dialog.

Enhancements and bug fixes for reports

The following enhancements and bug fixes are in addition to those already mentioned in relation to generating sentences for narrative reports:

  • In narrative reports, the <para> code did not work if followed by a space. That has been fixed.
  • In narrative reports, you could get a line starting with a full-stop, followed by a superscript for a source reference, if the sentence ended in a list of role names. This has been fixed.
  • With the Individual Summary Report, if you set the section label font to Calibri, you got garbage appearing. Now fixed.
  • Tightened up the use of the Private flag in narrative reports, outline reports and record detail reports, so that it is always honoured as you would expect.
  • Text expressions for heading text in reports were truncated to 150 characters. Now fixed.
  • If a record note was entirely private, you could get a full-stop appearing on its own in some reports, where private text was hidden. Now fixed.

Improvements for website generation

  • Fixed a layout issue with the display of images in generated websites when the images were laid out in rows along the top of a page, and there was more than one row.

The Family Historian Sample Project has been updated

  • The sample project now has more useful and more realistic data, especially with respect to sources and source certificates.

More enhancements for Family Tree Maker and Ancestry users

  • Family Historian now automatically checks for, and fixes, problems that arose when long text fields (notes, and other text fields) were incorrectly output to a GEDCOM file by Family Tree Maker (or potentially by other applications too). This means that some text fields which were previously truncated on import, will now contain the full version of the text. This fix works when a GEDCOM file containing incorrectly-handled text fields, is imported into Family Historian, but it also works when a project that had been created prior to the fix, is later re-opened within Family Historian. In other words, if you are a Family Tree Maker user, you do not need to repeat the import of your data into a Family Historian project. The problem is fixed automatically even with projects you have already created, when you next open them. This is possible because Family Historian previously stored the incorrectly handled text in extra hidden fields, within each record.
  • Family Historian now automatically checks for, and fixes, incorrectly located Title fields, within GEDCOM files (for pictures and other multimedia). Again, the main beneficiary of this change is likely to be Family Tree Maker users. And again, you do not need to re-import any GEDCOM files into a Family Historian project to benefit from the change. You should notice that Media records have correct titles, the next time you open a project which had exhibited the problem.
  • Family Historian now automatically installs a new fact set, called ‘Extended Set’. It is installed with lowest priority, so that it will not ‘eclipse’ any existing fact definitions. It provides fact definitions for well-known fact types used by Family Tree Maker and Ancestry; so that anyone who imports an FTM or Ancestry GEDCOM file into a new Family Historian project (or who opens a project that was originally created from an import from FTM or Ancestry), should see appropriate sentences if they generate a narrative report. The fact definitions in the Extended Set are all hidden by default, to avoid cluttering up the fact types list; but they can all be accessed and unhidden, and modified, if required.
  • Family Historian now supports all date formats that Family Tree Maker saves dates in, even if not valid GEDCOM (e.g. “BET MAY AND JUNE 1914″).

New date formats

  • There are two new preferred date format options in the General tab of Preferences: Preferred Standard Date and Preferred Short Date. Users can now choose to display dates month-first both for standard dates and short dates.

Improvements to the Property Box and the Witnesses Window

  • Improvements have been made to the function of the ‘Go Back’ button in the Property Box.
  • The Witnesses Window now disables the Sentence field when it is not applicable for the current selection.
  • A problem with handling of Julian dates – which arose when the dates were estimated, approximate or calculated – has been fixed.
  • A minor bug in the Property Box date entry helper dialog – which arose when switching between calendars – has also been fixed.
  • The Facts tab of the Property Box now only shows close relative events if they aren’t already listed.
  • Pressing Ctrl-A in a field (data entry box) is supposed to select all of the current text for that field. This did not work as it should have done in a number of fields in the Property Box. This has now been fixed.
  • The display of information in the ‘Sources For’ field of the Property Box’s yellow Source pane, has been tidied up – in part to present information more clearly when you are adding source citations for a witness.
  • If you added a citation for a child’s name, sex or birth in the Main tab of the Property Box, the citation was added correctly, but the source pane then showed source citations for the whole record, and not for the newly added item. This has been fixed.

Numerous enhancements for power-users

A brief reference was made to new power-user features in relation to sentence generation for narrative reports (see above). In more detail, the new features in this area were these:

  • The Insert Code button which features in the Fact Definition dialog and in the Edit Role dialog, produces a dropdown menu for inserting template codes into sentence templates (for principals and witnesses). It now has a new menu option for inserting data references, which makes them much easier to insert. Also, the Insert Data Reference dialog now automatically formats the inserted data references appropriately for the context into which they are being inserted (which normally means that they get percentage signs around them, except in narrative sentences where they have curly brackets and percentages signs around them).
  • Three new contextual data references (CUR_PRIN, CUR_PRIN2 and CUR~WITN) make it much easier to refer to principals and witnesses (and witness notes and roles) in narrative sentences, and to refer to any fields anywhere in their records, or in any records linked to theirs, directly or indirectly. For example, the expression {%CUR~WITN.ROLE%} references a witness’s role in a given event.
  • Data references beginning with ‘FACT’ did not previously work in the context of witness narrative sentences – e.g. {%FACT%}, {%FACT.DATE%} etc. This has now been fixed.
  • There is a new {blank} template code which is used on its own, when you want to prevent a sentence from being generated at all.

See also Enhancements and bug fixes for reports above.

Other enhancements for power-users include these new features and bug fixes:

  • There are two kinds of contextual data references: those which reference links and those which don’t. The ones that refer to links now begin ‘CUR~’ whereas the ones that don’t refer to links, begin ‘CUR_’. This makes it easier to see whether to use a chevron or not. Existing data references to links can be still use the ‘CUR_’ prefix for backward-compatibility, but this is depreciated, and the new form is encouraged henceforth.
  • There was a bug with some data references which used contextual data references. If you qualified a field in the context of some contextual data references, the expression was wrongly treated as invalid. This has been fixed.
  • Some contextual data references could not be inserted in the context of diagrams (for example, as expressions in box conditions). This has been fixed.
  • The Help for template codes and data references has been updated and improved. This includes the pages ‘Understanding Data References’ and ‘Template Codes’ amongst others. The updated pages describe the new shortcut codes and new contextual data references, in much more detail than previously, and use better examples.
  • The TimelineFactOrder function now honours the cutoff date, if there is one, that you can set for Timeline Facts in Preferences. This means that the Individual Timeline Query now behaves more like the Facts tab of the Property Box.
  • The TimeLineFactOrder function now returns a number for witnessed events. The TimeLineFactText function now returns text for witnessed events.
  • There is a new function, Sex, which takes up to 4 parameters, 3 of which are optional. These are a reference to an Individual, and the text to output if he/she is male, female or of unknown sex. The defaults are ‘male’, ‘female’ and nothing.
  • A new shortcut code for data references allows witnessed facts to be referenced for the Individual who witnessed them. The shortcut code is ~SHAR, and it is used with the INDI tag. For example %INDI.~SHAR[3]>% references the third witnessed fact for that individual. Direct ‘children’ of the ~SHAR code (i.e. if you use a dot after ~SHAR instead of a chevron) are children of the appropriate witness link. So, for example, %INDI.~SHAR[3]>DATE% references the date of the shared event. %INDI.~SHAR.ROLE% references the person’s role in that event. And so on.
  • Fixed bug with the FactOwner function (used in some queries).
  • Fixed bug with the IsAncestorOf and IsDescendantOf functions.
  • Corrected errors in examples and other errors in the Help page for the GetContextInfo function.
  • If you ran a query with a record parameter, and clicked ‘Browse…’ to pick one, when the Record Select dialog closed, the main application window would be re-enabled at that point. The Query Parameter Dialog although still open, was no longer modal. This has now been fixed.
  • Fixed a tooltip error in the Query Window for the ‘Save as’ option.
  • Text in the Rows tab of the Query Window, was missing some operators (such as ‘Contains’) if the expression was a link to a record. This has now been fixed.

Numerous other enhancements and bug fixes

  • In Field Lists (such as on the left side of the Columns tab of the Query Window), child fields of a link field now have brackets round their field names so that they are easy to distinguish from fields in the linked record.
  • There is a now a preview option for image files in the Work with External File Links tool.
  • The New Source dialog now has a dropdown list of Source Types.
  • The background grid colour of the Diagram Window has been darkened slightly, to make the grid stand out more clearly.
  • Fixed a bug that arose when a framed picture was rotated in a diagram.
  • The ‘Paste Image’ menu command on the Media menu was redundant, and permanently disabled. It has now been removed.
  • Sorting on the Latitude/longitude column in the Places tab of the Records Window did not work. This has been fixed.
  • The green arrow button on the Lists toolbar (visible when the Records Window is active) is used to add a selection to the current Named List. It is now only ungreyed when a record is selected.
  • Drag-and-drop from a web-page did not always work as it should. This has been fixed.
  • Previously drag-and-drop only worked with picture files, when dropping the files onto special ‘drop zones’ (such as the Media Viewer or the Media tab of the Property Box). But any file can be treated as ‘Other Media’, so now you can drop any kind of file in any drop zone.
  • When filtering Place records in record lists, if you typed in a place name, it wouldn’t match places where the place name was immediately preceded by a comma. This has been fixed.
  • It has been made easier to switch from viewing media in the Media Viewer to showing the same media in the workspace Media Window. Right-clicking on a thumbnail provides convenient options for this, and for viewing the same media in an editor/player.
  • Various enhancements have been made to the way the Media Viewer interacts with the Property Box, to ensure that it always behaves as you would expect.
  • The position and size of the Media Viewer is now saved persistently between sessions.
  • Some users reported that some preference settings reverted to installation defaults, when they upgraded to a new version of Family Historian. This has been fixed.
  • Family Historian now does a better job of importing Ancestry GEDCOM files, by automatically solving a number of problems when the files are imported. Previously, for example, you could end up with numerous Media records for the same media file. This is now much less likely to happen.
  • There has been a performance enhancement which should improve the speed of plugins – in some cases, quite considerably.
  • The Media Viewer has a new ‘View’ button. Clicking this button gives a choice of the currently selected media in an external viewer/player, or viewing its record in the Property Box. A third option allows all media currently showing in the Media Viewer, to be displayed instead in the workspace Media Window.
  • Family Historian will still, optionally, save fields it does not recognise as ‘Uncategorised Data Fields’ (UDFs). When a GEDCOM file is imported, any UDFs that store links between records (UDF links) are now updated, if necessary, during the import to ensure that the link information they store is correct, and uses the correct record ids after the import, even if records have been renumbered.
  • Various improvements have been made to the handling of log files. Also, they are now stored in UTF-8 format.
  • The ‘Spouse Parents’ option did not work correctly in some narrative reports. This has been fixed. Also, in rare circumstances, a spurious full-stop could appear in some sentences. That too has been fixed.
  • Family Historian now shows burial or cremation date or place details in the Focus Window, if there are such details, and if there are no date or place details for the death event (if there is one).
  • When importing a GEDCOM file into a new project, an unwanted extra space could sometimes be added into the odd gap between words, in multi-line text. That has now been fixed.
  • A filtering bug in the Records Window, which affected Media, Place, Repository and Source tabs, has now been fixed.
  • A bug when entering some ‘double dates’ (such as ‘Jan 1624/25 est’) has now been fixed.
  • The description at the bottom of the Columns tab in the Query Window was wrong for Place records, and its ‘child’ Text field, and for Note records. This has been fixed.
  • When opting to view linked media in the workspace Media Window (from the Media tab of the Property Box), the Associated Events/Facts option did not work correctly. This has been fixed.
  • When adding a single media file to a project, if you opt to copy the file into the project, Family Historian now automatically offers to modify the copy’s name to make it unique if otherwise there would be a name clash with an existing file.
  • The diagram option (part of the group relating to markers for people who have no offspring) to ‘Also put marker below individuals with no spouses & no children’ did not work. This has been fixed.
  • Various other improvements, over and above those already mentioned, have been made to the Help (and Plugin Help).

New in 6.0.4 (Mar 2015)

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.

New in 6.0.3 (Mar 2015)

TMG Import Enhancements

  • Source elements are now imported as labelled values within source record notes.
  • Previously if an Individual event had 2 (unmarried) 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 below), 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 <br> or <para> at the start – because the text would 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 in the Tools menu.
  • 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 be 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.

New in 6.0.2 (Feb 2015)

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.

New in 6.0.1 (Jan 2015)

TMG Import Enhancements

  • Import of The Master Genealogist files previously crashed if the file contained Witness memos. Now 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.