Upgrade to Version 6.1

Pre-release Upgrade to 6.1 (version 6 users only)

UPDATE (Feb 20th, 2016): The pre-release version has now been updated to 6.1.4.  See New & Enhanced Features in 6.1.4 below.

Version 6.1 is an important and substantial new update to Family Historian 6.  Users of version 6 can now download this pre-release free upgrade to Family Historian 6.1.  ‘Pre-release’ means that the software has not been officially released yet.

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.

Please note that the book Getting the Most from Family Historian 6 (due to be published shortly) will recommend that all users should be on version 6.1.

Comments about version 6.1 can be posted to the New Pre-release 6.1.4 thread in the General Usage forum of the Family Historian User Group website.

Download “Family Historian 6.1.4 Upgrade” – Downloaded 7505 times –


ENHANCEMENTS AND BUG FIXES IN VERSION 6.1 (and 6.1.1, 6.1.2, 6.1.3 & 6.1.4)

Click items to view details.  See also Definitions of Terms below.

+ New & Enhanced Features in 6.1.4

  • The periodic cycles of Automatic Snapshots are now configurable in Advanced settings (see the General tab of Preferences).
  • Previously there could sometimes be problems with fact names when generating fact definitions for facts, imported from TMG, if the fact names contained hyphens. This has now been fixed.
  • Fixed bug with the menu button on the Source pane toolbar.

+ New & Enhanced Features in 6.1.3

  • Family Historian now has the capability to automatically take and store periodic snapshots of each project’s GEDCOM file.  You can also revert to a recent snapshot if you wish.  These snapshots should not be viewed as a substitute for regular backups, but they provide a useful additional layer of protection against various possible problems.  The facility is enabled by default, but can be disabled in Preferences if required (File Load/Save tab).  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’.  At most only one snapshot is ever taken each day for each project, and only if you save changes. At most 8 snapshots are kept for each project (new ones replace old ones).  This is to ensure that the space taken by snapshots never becomes excessive.
  • Clicking the ‘Show Media’ button on the toolbar of the Source Citation Pane in the Property Box still shows all media associated with the selected source citation in the ‘Show Media’ dialog.  But you can choose, at the top of the dialog, whether to view media for the citation, or media for the Source record.  The tick options show the number of media files of each type, so you can see how many there are, without having to tick the option.  If you view citation media, the ‘Add’ button allows you to add citation media.  If you view Source record media, the ‘Add’ button allows you to add Source record media.  Your last-used option is remembered, so if you only ever use one or the other, you never need to view the media type you never use.
  • Various methods have been used to make it clearer what kind of media you are viewing in these circumstances (media for a citation or media for a Source record).  The text of the ‘Add’ button changes appropriately (it will say ‘Add Media for Citation’, ‘Add Media for Source Record’ or ‘Add Media for Fact’ as appropriate).  Also, if there is no media, a centred prompt message says ‘Drag media files here, or click Add Media to add media for Source record’ (or ‘for citation’ or ‘for fact’ depending on the context).   The prompt helps to make it clear what happens when media are added, but also provides a useful reminder that you can drag-and-drop media files here.  A similar prompt is also now used in the Media tab of the Property Box, to remind the user that these are also ‘drop zones’ for dragging-and-dropping media files.
  • Previously drag-and-drop only worked with picture files.  But any file can be treated as ‘Other Media’, so you can now drop any kind of file in drop zones.
  • Users who prefer to view media in the workspace Media Window, can now use a new menu button on the Source Citation pane toolbar to do so.  You can also use the same menu to open media in an editor/player.  Both options are disabled if there is no source citation media for a given source citation.
  • It has been made easier to switch from viewing media in the Show Media dialog (sometimes now called 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 Show Media dialog interacts with the Property Box, to ensure that it always behaves as you would expect.
  • The position of the Show Media dialog is now saved persistently between sessions.
  • Some contextual data references could not be inserted from the Insert Data Reference dialog, because when you selected them and clicked ‘Add’ you would be told that they were invalid.  This was supposed to be fixed in a previous update, but some issues remained.  These have now been fixed.
  • Some users reported that some preference settings reverted to installation defaults, when they upgraded to a new version of Family Historian.  We believe that this problem 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.

+ New & Enhanced Features in 6.1.2

  • Clicking the ‘Show Media’ button on the toolbar of the Source Citation Pane in the Property Box now shows all media associated with the selected citation in the ‘Show Media’ dialog.  A new checkbox on that dialog now allows source record media associated with the current citation, to optionally also be displayed.  The button icon has been changed to better reflect its new role (it matches the equivalent button on the Facts tab toolbar).
  • The ‘Show Media’ dialog is also used to show media for a selected fact in the Fact tab of the Property Box.  When showing media for a fact, there are now two new check boxes which allow you to optionally show both citation media and source record media associated with that fact.
  • When the ‘Show Media’ dialog is open, simply clicking on a fact in the Fact tab, or a citation in the Source citation pane, will cause the ‘Show Media’ dialog to automatically update itself appropriately, to reflect the current selection.  The ‘Show Media’ dialog caption indicates which item media are currently being shown for.  The new checkboxes do not affect the behaviour of the ‘Add’ button which will always add either citation media for the currently selected citation, or fact media for the currently selected fact, depending on the context.
  • The ‘Show Media’ dialog 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 ‘Show Media’ dialog, to be displayed instead in the Media Window.
  • Family Historian now recognises all extensions to GEDCOM used by Family Tree Maker 2014, even including ones that are not prefixed by an underscore (e.g. _MILT, EMAIL, etc).  When a GEDCOM file is imported into a new Family Historian project, any such extensions will by default be automatically converted to valid events or attributes, or incorporated into the program in an appropriate way.  A new Preferences option (‘File Load/Save’ tab) allows this to be prevented, if desired.
  • Family Historian now automatically installs a new fact set, called ‘Extended Set’, if no such fact set exists.  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 2014; so that anyone who imports an FTM GEDCOM file into a new Family Historian project (or previously did so), should see appropriate sentences if they generate a narrative report.  The fact defintions 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, if necessary (e.g. if someone wishes to modify them).
  • A new option on the same tab of Preferences (enabled by default) now means that when a GEDCOM file is imported into a new project, spouses, children and siblings are all automatically sorted into the correct order, if not already in the correct order.
  • 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 validated during the import, so that the stored information remains correct after the import, even if records have been renumbered.
  • Users who imported a project into Family Historian before 6.1.2 was released, can take advantage of its capacity to recognise GEDCOM extensions used by Family Tree Maker 2014 by using a new command “Recover Uncategorised Data” (click ‘Tools’ and then ‘Uncategorised Data’).  When this command is run, Family Historian will put up a warning message about UDF fields that contain links, if there is a risk that the link information in the UDF may be wrong (because the fields were created before the previous feature, for automatically updating UDF links, had been implemented).
  • The Preferences option to save in UTF-8 format was not being preserved between sessions.  That has now been fixed.
  • 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.  Now fixed.  Also, in rare circumstances, a spurious full-stop could appear in some sentences.  That too has been fixed.
  • Family Historian hopefully now supports all date formats that Family Tree Maker saves dates in, even if not valid GEDCOM (e.g. “BET MAY AND JUNE 1914”).
  • 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).
  • In unusual circumstances, Record Window options in Preferences could apparently revert to installation defaults, following an upgrade.  That has now been fixed.
  • 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.
  • In previous versions of 6.1, Family Historian tries to handle incorrect uses of the CONC tag by Family Tree Maker.  One further case, previously missed, has been identified and is now also handled.

+ New & Enhanced Features in 6.1.1

  • New option in Property Box tab of Preferences, allows user to choose to display slashes round surnames in the Property Box, either ‘Always’ or ‘Only When Necessary’ (the default).  Latter option means that no slashes will be shown round the surname if there is more than one word in the name, and the last word is the surname. If you enter a one-word name, you will be warned (until you indicate that you no longer wish to be warned) that  slashes will automatically be appended (e.g. “Jane” becomes “Jane //”).
  • 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.
  • 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 Text field child, and for Note records. This has been fixed.
  • When opting to view linked media in the Records Window (from the Media tab of the Property Box), the Associated Events/Facts option did not work.  Now fixed.
  • When adding a link to a place record in the Media Window, spurious text has been removed from the Place record selection dialog.
  • 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.
  • Improvement to the TMG import: A number of enhancements have been made to the handling of names on import. Prefixes and suffixes are now handled correctly. The TMG ‘Title’ field is handled as another prefix (prededing the ‘Prefix’ field, if both are supplied). The ‘preSurname’ field, if used, is inserted before the surname. The ‘Other Name’ field, if used, is inserted into the Family Historian Nickname field. Surnames are no longer capitalised on load. Name parts which begin with a hyphen are ignored.
  • 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. Now fixed.
  • One fix to a power-user feature: some contextual data references could not be inserted from the Insert Data Reference dialog (e.g. “%CUR_FILE_OWNER%” when inserted in the context of an Individual Summary Report).  This has been fixed.
  • Various improvements have been made to the Help (and Plugin Help).

+ Witnesses can now have multiple roles, and a principal can also be a witness

For a witness to have multiple roles with respect to a given event, just add them as  a witness more than once for that event, with different roles.  A principal can also be a witness to their own event, with more than one role if required. It is not uncommon for people to have multiple roles with respect to events – for example, an executor of a will may also be a beneficiary. Now you can record this and view it as you would expect in the Witnesses window and in the Facts tab of the Property Box. However many roles a person has, they will still only ever get at most one sentence describing their role(s) in any given event. You can reference list of people with a specific role (beneficiaries, say), and refer to it in narrative sentences, and this works as you would expect. Where a person has multiple roles, sentences may sometimes need a little tweaking to get best results.

+ You can now effectively have no-principal or multi-principal events

Most events (like birth and death) are treated as having one person who is the principal. A few (like marriage) have two. 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 add all five to the same event as witnesses, 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.

+ You can now add source citations for relationship information

You can add a source citation for a husband-wife relationship by adding source citations for the marriage event. This is not new. The new feature is that you can now also add source citations for parent-child relationships. This is done using the witness functionality. To record that a person, X, was the father of a child, Y, you should add X as a witness to the birth of child Y, with role of father or parent. Then you can add source citations for X in their role as father or parent. By default, these roles are defined so that you will not get extra, unwanted sentences appearing in reports. Obviously you use the same approach for the mother-child relationship. If a child is adopted, you take the same approach with the adoption event, adding the parent as adoptive-father, adoptive-mother, or adoptive-parent.

+ Much improved support 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 enhancements and new features in this area are likely to be primarily of interest to power-users:

  • 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.  Search for ‘Template Codes’ and ‘Understanding Data References’ in the Help for more details.  Both pages have been improved with more examples – such as the expression to use for accessing witness notes.
  • 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 do want to prevent a sentence from being generated at all.

See also Enhancements and bug fixes for reports below.

+ The alternative map type for the Map Window now works once again

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.

+ Problems with missing pictures can now be fixed automatically

If any pictures are missing (that is, if there are any links to media files which aren’t working) following an import, you will be prompted to let Family Historian automatically fix the broken links by searching for the missing files on your PC.  This functionality can be invoked at any time by clicking on the new Auto Repair Links button in the Work with External File Links tool.

+ New Witnessed Events query

The new Witnesses 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.

+ Option to improve compatibility with other programs (using UTF-8)

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 your needing to export it.  The default however is still UTF-16 (formally equivalent to UTF-8, but less widely supported by other applications).

+ 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 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 layout issue with display of images in generated websites when the images are laid out in rows along the top of a page in reports, and you have 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.

+ Enhancements for Family Tree Maker users (primarily)

  • 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 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.
  • New date formats (requested by FTM users – added in 6.1.1 see above).
  • New option to avoid showing slashes round surnames in the Property Box (requested by FTM users – see 6.1.1 above).

+ Enhancements for Genbox users

The direct import from Genbox has been enhanced as follows:

  • 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).

+ Enhancement for TMG users

There have been a number of enhancements which are of particular interest to users of The Master Genealogist (TMG).  There have been improvements to the TMG Import:

  • 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 import of “internal text” files under the “exhibit” tab. Only the first 300 words (approx.) of each text file came across.  This also has been fixed.
  • See enhancements in 6.1.1 above, for improvements to the handling of names, in TMG imports.

In addition, various new features that have already been mentioned are likely to be of particular interest to TMG users, such as:

  • The facility to automatically find missing pictures and media files if necessary, after an import.
  • Effective support for no-principal and multi-principal events.
  • The ability to add source citations for relationship information.
  • Improved support for generating sentences in narrative reports.
  • Sundry enhancements and bug fixes with respect to witnesses.

+ Improvements to the Property Box and the Witnesses Window

  • Improved function for ‘Go Back’ button in Property Box
  • The Witnesses Window now disables the Sentence field when it is not applicable for the current selection.
  • Fixed bug with handling of Julian dates, when estimated, approximate or calculated.
  • Fixed minor bug in Property Box date entry helper dialog when switching between calendars
  • The Fact tab of the Property Box now only shows close relative events if they aren’t already listed.
  • Ctrl-A did not work in a number of fields in the Property Box that it should have worked in. Now fixed.
  • The display of information in the ‘Sources For’ field of the Property Box’s 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.  Now fixed.

+ Improved support for companion products

  • 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, in UTF-16 LE format, with a BOM 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.

+ Numerous enhancements (and bug fixes) for power-users

We have already discussed some features that are likely to be of particular interest to power-users (experts) in relation to generating narrative reports.  In addition to those, there are also 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.
  • Many 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 “Understanding Data References” and “Template Codes” & other pages, has been updated.  The new versions detail the new shortcut codes and new contextual data references, in much more detail than previously and with examples to make it easier to understand and use.
  • 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.
  • =TimeLineFactOrder function now returns a number for witnessed events. =TimeLineFactText now returns text for witnessed events
  • Threre 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.  Defaults are “male” and”female”.  The male text is used if no text is specified for people of unknown sex.
  • 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 fact.  And so on.
  • Fixed bug with =FactOwner() call in query
  • Fixed bug with IsAncestorOf and IsDescendantOf functions.
  • Corrected incorrect examples and other errors in Help page for 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 – i.e. the Query Parameter Dialog although still open, was no longer modal. Now Fixed.
  • Fixed tooltip error in the Query Window for ‘Save as’ option.
  • Text in Row tab was missing operator (e.g. ‘Contains’) if the expression was a link to a record. Now fixed.

+ Numerous other enhancements and bug fixes

  • Numerous other improvements to the Help.
  • In Field Lists (e.g. in left side of the Columns tab of the Query window), same-record children of a link now have brackets round their field names so that they are easy to distinguish from fields in the linked record.
  • Fixed a bug with Undo/Redo in relation to Witness information.
  • 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.
  • Slightly darkened the background grid colour of the Diagram Window, to make the grid stand out more clearly.
  • Fixed bug when rotating a framed picture in a diagram
  • Deleted redundant (permanently disabled) “Paste Image” menu command on the Media menu
  • Sorting on the Latitude/longitude column in the Places tab of the Records Window did not work. Now fixed.
  • Green Arrow button to add selection to the current Named List, is now only ungreyed when a record is selected.
  • Drag-and-drop from a web-page onto the Fact Media Dialog and Place Rec Dialog special drop zones, and onto the main application window, did not work. Now fixed.
  • The text “Standard Query (read only)” was truncated in the Query Window. Now fixed.
  • Resetting the sample project now clears saved charts and saved books.
  • When filtering record lists, if you typed in some place name, it wouldn’t match places where the place name was immediately preceded by a comma. Now fixed.


Witnesses & Principals

The term ‘witness’ is used in a slightly technical way in this context and does not just mean people who literally witnessed something, in the ordinary sense.  It is the term used for people who participate in events, in a non-principal role – for example, the best man and bridesmaids at a wedding count as witnesses, whereas the bride and groom are principals.  For a will event, the person making the will is the principal, and executors and beneficiaries are examples of witnesses.  With witnesses, you always have to specify the person’s role.


Expert in using the program, who makes use of advanced features.

Data Reference

A kind of code that can can be used to refer to a specific bit of data (the actual date field in which a person’s date-of-birth is recorded, say, or even a specific source citation for it).  In various contexts, data references can be used to refer to items of data, when passing instructions of various kinds, to Family Historian.  Ordinary users have little need to be aware of data references, but they are much used by power users, as part of some of the advanced features.

Contextual Data Reference

A particular kind of data reference which only works in specific contexts.

63 queries. 0.605 seconds. Current Time:24-10-16 12:12:53 UTC