Family Historian User Group

We have now created a new patch (5.0.5) which fixes the bug that BrianP discovered in 5.0.4. We strongly recommend everyone who upgraded to 5.0.4 to upgrade again now to 5.0.5 (see http://www.family-historian.co.uk/downl ... ee-upgrade).

This is just to say that we have confirmed that there is indeed a bug in 5.0.4 as reported, which can have the effect that line endings in notes can be lost. We will put up a fix for this as a matter of urgency.

We have confirmed that there is a bug in the way that pools are calculated in 5.0.2.  I'm sorry about that.  We are testing a fix to it now, and hope to release it as a patch update shortly.

We believe we've now fixed this problem in a patch (5.0.2) which also fixes various other problems. Anyone who has experienced this problem should download and install the patch at http://www.family-historian.co.uk/downloads/latest-free-upgrade If you still have problems even after installing the pa...

Thanks for pointing that out! It has now been fixed.

This isn't a bug - it's a feature of Lua. Within Lua, the backslash character '' has a special role in strings (as it does in other programming languages like C and C++). For example, 'n' means the newline character and 't' means a tab character. If you want to put a backslash into a string, you hav...

We've only just noticed that we have had two functions which do almost the same thing.  These were fhGetItemText and fhGetDisplayText.  The only difference between the two is that fhGetItemText took a data reference as a second parameter so you could have a line like this: fhGetItemText(ind, '~.OCCU...

Hi I would just like to confirm what both Jane and Tatewise have said on this.  The problem (as is mentioned in the link that Tatewise gives) is that the option to 'Exclude all records which are not linked to the selected Individual records', in Export Gedcom File, is interpreted by FH as meaning 'd...

McAfee say that they have now fixed the problem.  Please see the discussion in the V4 usage forum: http://www.fhug.org.uk/cgi-bin/index.cg ... 6&start=90

We have now heard back from McAfee.  I'm very pleased to say that they say they've fixed the problem!   They say: 'This issue has been corrected. Please instruct your users to update their McAfee protection to the latest DAT version 6475 released today [i.e. yesterday - tuesday]'.  I suspect that th...

We'd like to firm up some of the details of this problem  if possible.  Could everyone who has experienced this problem please post to say: (a) Exactly what McAfee products you have.  Please also give the full version number of each McAfee product. (b) The date that the problem started (c) Confirmat...

I have spent a large part of today trying to get through to McAfee by all available means, and so far have not received any firm confirmation that they have even logged the problem.  The only people I have been able to get through to is their Technical Support service, and they say that that it is t...

Thank you very much for everyone who has posted to this forum.  I can confirm that we also have received numerous reports of this problem, and yes indeed it does appear to be a problem with McAfee. We have already emailed McAfee and asked them to fix the problem.  We are asking everyone affected to ...

I can confirm that fhGetDisplayText will be modified in 5.0.0.3 as Jane says, to give improved summaries for data item - e.g. attributes.

It occurred to me after reading Chris's post that there really should be a way to add records mentioned in query output, generated by plugins, to a Named List; so there will be a new function 'Add Selected Cell Records to Named List', on the query menu, to do this - in version 5.0.0.3.

Currently if you double-click on a 'Where with Source' cell for that query, FH will take you to the Main tab of the Property Box if the source is for a Name field. That doesn't feel right. Unless you explicitly specify that you want 'Locate in All Tab', Fh will try to find the most appropriate tab f...

You can't currently add the records generated by a plugin query to a named list. Out of interest though, why not use the query result set itself as the way to quickly locate the records and fields you wish to update? If you double click on a cell which contains a record, it will be shown in the prop...

Thank you for pointing these issues out. They will all be fixed in the next release.

Thank you for pointing this out.  It will be fixed in the next release.

Have you considered hiding all the events and attributes you rarely use? That way, the ones you use a lot should be much more easily accessible. Click the 'More' to show the Hide button. Press the Ctrl key while clicking on list items to select multiple discontiguous items, and then click 'Hide' to ...

Tatewise - I have had a quick look at your example, and agree that it doesn't match what I said - thank you for pointing that out.  It's a somewhat complicated area because as well as, effectively, 2 kinds of date comparison - the sort kind and the calculation kind - you also have 2 kinds of dates: ...

Tatewise - Family Historian's date sort algorithm does not simply use the date comparison operators because the requirements of the two are different.  Date sorting should present dates in an order that is presentationally most convenient for most users, most of the time. The job of the comparison o...

All functions, whatever their return type, can effectively return a null value if there is no value to return.  It's not obvious to me that it is more desirable to return 0 rather than blank, in such cases.  Blank cells in queries are surely easier to filter out visually.  Also, in some contexts a v...

It is true that you cannot test for an empty string using either IsEmpty() or NullDate() - but neither of them are designed for that.  IsEmpty() is used to test whether a data item exists or has no value.  NullDate() is used to test whether a date is Null. To test whether a string is empty, you shou...

Thank you all.  We have taken note of this issue and will investigate it.  Meanwhile, to work round it, you could either revert to the default font, or experiment with other fonts that don't have the problem.