Views and their program dependencies

Help
1

Apropos of nothing in particular

Whilst in Person View was looking at the Events window and saw the age column which I never have visible usually so thought why do I not just deselect that column and of course you cannot or at least not as far as I can find through Preferences and there is no Configure option. Only age I would require is “Age at Death” and that would be in the form “In the 82nd year of his/her age” as per most UK headstones and thus a rounded up year.

So went onto think about maybe having a go at a little programme hacking but cannot find any information for Views which shows the dependent programs otherwise it is hit and miss looking at hundreds of files in numerous sub folders.

Is there a document I can find somewhere which does list each View and the programs upon which it is dependent.
Phil
A program tweaker not programmer
GRAMPS: 5.1.6
Python: 3.10.12 (main, Nov 20 2023, 15:14:05)
BSDDB: 6.2.9 (5, 3, 28)
sqlite: 3.37.2 (2.6.0)
LANG: en_GB.UTF-8
OS: Linux
Distribution: 6.2.0-39-generic

2

In Preferences you can set the Age precision to Year, Year and Month, or Year Month Day, in Gramps 5.1, When set to Year the age will round up after six months. In 5.2 an added option would have the year age option not round up. It will also add an option to not show the age for any events after death, i.e. Burial, Probate of a will, etc.

No, you cannot turn age on/off. You could hack the code to remove the age column from the events. If you were to do that, the age at death would only display for the active person in the Relationships view.

3

Sorry! This is an option that may not make it into 5.2 as it was proposed after the code was sent out to the translators.

4

Thanks Dave

Will think about that but the reason I do not use it is for death it
should round up on day 1 so 81 and 1 day = 82nd year
Please do not worry about it.
Phil

5

I can show you where in the code that decisions are made. But this would be your hack. Users wanting any change were advocating for no rounding.

Here is the bug discussion and the proposed fix. If nothing else, it points you to the code so you could make a hack for yourself.

https://gramps-project.org/bugs/view.php?id=12422

6

Dave

Thanks very much I was not really looking to see my requirement
implemented as a standard and well understand/support why people do not
want rounding so will look at program with interest.

Phil

7

Actually, the discussion was choosing between “round up” and “round down”.

In the US, a person who dies when their 38th birthday would be the next day is still will be listed as age 37. Although an anniversary that near normally gets a mention too.

8

Brian

If I have an individual where I have only the Birth and Death
Registration by Quarter

Say birth bet 22 Nov 1846 and 31 Mar 1847
and death bet 17 Jun 1898 and 30 Sep 1898

The age at death calculation is pure nonsense as is every event
throughout the life of the individual.
So rounding up or down is irrelevant if I really wanted to calculate age
at death I would have a simple date field in which I entered the value
thus “approx/circa 85”.
So for me you could eliminate all age calculations and I would not miss
them but guess that is not an option
Phil

9

You might want to read the discussion about Quarter support on GitHub:

With the Feb 2022 push, it should be in the upcoming 5.2 release.

10

Go to you programs files folder. Edit the file…
gramps\gui\editors\displaytabs\eventembedlist.py

Edit line 202

    return ((1, 1),  # type
            (1, 0),  # description
            (1, 3),  # date
            (1, 4),  # place
            (1, 6),  # main participants
            (1, 12), # private
            (1, 5),  # role
            (1, 2),  # gramps id
            (1, 10),  # age
            )

by adding a hashtag (#) before the age option.

    return ((1, 1),  # type
            (1, 0),  # description
            (1, 3),  # date
            (1, 4),  # place
            (1, 6),  # main participants
            (1, 12), # private
            (1, 5),  # role
            (1, 2),  # gramps id
            #(1, 10),  # age
            )

Save and relaunch Gramps. The age will no longer appear in the event lists. As I said, the age at death (or still alive) will appear for the active person in the relationships view.

Note: You will need to edit the file when the next leases of Gramps come out.

11

Brian

Whilst Quarters is a good idea in principle in fact they do not really
exist as such
If you look at my previous example you would ask why they do not start
at the first of the month.
The answers are as follows in the UK you are allowed 40 days after the
birth to register the birth therefore I calculate 40 days before the 1st
day of the Quarter
Death can occur several days before the end of a quarter and the
registration delayed to the next quarter for a variety or reasons.
Christmas/New Year being one of the classics

Phil

12

Thanks Dave
Will play with that a little.
Problem is of course documenting all the “fixes” you have done as an
individual.
Phil

13

For each modification I make I add the comment #DES_MOD at the end of the line. I then save a copy of the file in a Modification folder duplicating the folder structure.

I now have a record of the changes I have made for the next release. Just remember that official changes to the code may be made so the next change may not occur on line 202.

14

Just saying it was added. Personally, more of my sources found from the post-Revolutionary War sources in America tend to use ‘seasons’ rather than ‘Quarters’. Not sure whether I will use Quarters either. But… it is there.

Ass for your example:

Ages for each event will be calculated to figure minimums and maximums. So age at death will be a range from the (latest birth to earliest death) and (earliest birth to latest death)

  • age of between 51 years, 2 months and 51 years, 10 months
15

Thanks Dave

Done that works as expected.
I annotate with #PW 01/01/2024 Proven or Test
Keep mod info on a Document with the file path as a header for that section.
Phil

16

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.