* Individual Property Box - Place/Address

[dhwalt]

The Fact Column uses the Place variable. Is it possible for a user preference that allows concatenation Place + Address to be displayed? I am not asking that Place + Address be stored as a 'Place'. An example - address, place in the Fact column.

Fact Column.jpg (239.7 KiB) Viewed 677 times

For the above ALL Fact addresses are updated to address, place i.e. see highlighted row Consett... changes to 3 Hartington Street, Consett...

Thanks David

[ColeValleyGirl]

What do you mean by the Fact column? The Fact Tab?

A screenshot of what you mean would make it clearer.

P.S. I'm moving this to the General Usage forum for discussion of whether what you want is already possible; it will get moved back here if the conclusion is that it isn't.

[tatewise]

Assuming you are talking about the Facts tab, Fact column then it can be customised in many ways.
Use Tools > Fact Types... and Edit... the fact definition.
Click the Advanced... button, tick Summary Template and enter a Template definition such as:
Born {place}< at {address}>
It uses much the same rules as Sentence Templates but not all codes and functions are supported.

See FH Help page Fact Definition - Advanced Features Dialog.

[Mark1834]

Presumably, usual caveat applies - if you are editing a Standard Fact, it is best to create a copy in your Custom Fact Set to avoid the modifications being blown away in a future update of FH.

I had a go at modifying the custom attribute that I use to denote marriage for end-of-line individuals where I don't want to create a new family, and it worked well there.

Individual.PNG (8.68 KiB) Viewed 619 times

I then tried adding the place of the marriage to my custom copy of the standard Marriage fact, but that didn't seem to pick up the name of the spouse correctly, even though I added the fields from the helper data entry screen. Have I missed something, or is it a bug?

Family.PNG (13.51 KiB) Viewed 619 times

[tatewise]

FH updates don't usually alter even the standard fact definitions.
The Restore Defaults button is intended to reset to installation settings.
Anyway, the Backup and Restore FH Settings... plugins preserve the customisations.

You have discovered one of the unsupported codes that I mentioned.

I reported those problems in August 2020:

Family Advanced Override Template Problems #497713
This relates to Tools > Fact Types for any Family event such as Engagement, Marriage, Divorce, etc.
In the Edit Definition the Advanced… button opens Override Templates for Facts tab & Records Window.
Most codes and contextual data references do not behave as might be expected for Family facts.

In the Facts tab, a suffix such as to John Smith or from Jane Doe is always added unconditionally.

For example, it seems impossible to display the fully adorned name of the spouse by using such as:
Marriage to {spouse/her/him} or Divorce from {%CUR_PRIN2.NAME[1]%}.

That was partly fixed in FH 7.0.0.6 because to John Smith is not now unconditional, and {%CUR_PRIN2.NAME[1]%} works as a substitute for {spouse/her/him}.

[AdrianBruce]

FH updates don't usually alter even the standard fact definitions. ...

Conversely, that isn't necessarily "a good thing". I had altered some fact definitions and indeed, they remained untouched during updates of FH. It may have been after the introduction of witnesses that I searched for inspiration on how to use them. But the narrative sentences, etc., studiously ignored them - well, of course they did, because effectively I'd frozen them. It then became a little bit more difficult than it could have been, for me to see what Calico Pie had provided for sentences using witnesses in relation to birth or whatever it was.

[tatewise]

This discussion is in danger of straying from the primary topic, but mostly all customisations of standard features are preserved when FH is updated (i.e. Tools > Preferences, Diagrams, Text Schemes, Reports, Fact Sets, Property Box tabs, etc, etc).
Again I say that is where the Restore Defaults buttons and backups come into play.
Interestingly, standard Queries cannot be customised, so why not similarly freeze all other standard features and require cloned copies to be customised just like Queries?

[AdrianBruce]

... Again I say that is where the Restore Defaults buttons and backups come into play. ...

Agreed. It does, however, need a bit of thought to map out a way that (a) makes visible the CP modifications (via Restore Defaults presumably) and (b) doesn't throw away the bits you've previously done. Preferably doing the thought bit first! (Oddly the contents of the Old Versions button doesn't appear to be updated when you Restore the Defaults?)

... Interestingly, standard Queries cannot be customised, so why not similarly freeze all other standard features and require cloned copies to be customised just like Queries?

I agree - a touch of inconsistency.

[Mark1834]

Disappointing that something that is definitely wrong (rather than just cosmetic) hasn’t been fixed after all that time. Good to know that FH is more reliable for saving customisations but being able to easily switch between standard and custom versions of facts and reports, etc, feels much easier than backups and defaults so I’ll carry on working that way.

Added in edit - I raised this with CP last night, and the gist of their answer appears to be that the functions are behaving as planned, but it is the documentation that is inconsistent. The good news is that the rather cryptic alternative notation that Mike posted yesterday can be readily generated using << Insert Code > Data Reference..., so at least the workaround is fairly straightforward.

Family2.PNG (7.45 KiB) Viewed 504 times

[tatewise]

Yes, it is strange that CP fixed {%CUR_PRIN2.NAME[1]%} to work but not {spouse/her/him}.
If I recall correctly there are other bugs too, such as {couple} does not work.

What inconsistent documentation are CP referring to?
FH Help page Fact Definition - Advanced Features Dialog does not mention codes or functions other than to cross-refer to the Sentence Template Codes, which do say "Principal sentences only." for {spouse/her/him} and {couple}. So perhaps that means they don't work in Advanced Templates.