gramps-users

I notice that the record gramplet doesn't properly calculate, for
example, longest marriage. It merely reports the difference between the
date of a marriage and the latest death of a spouse. It should instead be
looking for the earliest death of a spouse. (What should it do where no
death is recorded? I think it should return nothing.)
Do other users get similar results?
--
Martin

Hi, Martin,
Am Freitag, den 13.03.2009, 01:48 +1100 schrieb Martin Steer:
> It merely reports the difference between the date of a marriage and
> the latest death of a spouse. It should instead be looking for the
> earliest death of a spouse.
That's what it does for me. However, I must confess that I didn't try
3.1 yet, this is 3.0 here.
> (What should it do where no death is recorded? I think it should
> return nothing.)
There are 2 distinct records:
* "Couple married most long ago" for the oldest still intact marriage
* "Longest marriage" for the longest marriage which has already ended
(either by death of one of the spouses, or by divorce)
If both spouses are still alive and they are not divorced, they simply
don't qualify for the "Longest marriage" record.
Thanks,
Reinhard

Hi Reinhard,
Reinhard Müller <reinhard.mueller@...> writes:
> Am Freitag, den 13.03.2009, 01:48 +1100 schrieb Martin Steer:
>> It merely reports the difference between the date of a marriage and
>> the latest death of a spouse. It should instead be looking for the
>> earliest death of a spouse.
>
> That's what it does for me. However, I must confess that I didn't try
> 3.1 yet, this is 3.0 here.
>
Sorry, I should have said that I was using gramps31, via svn. Are you
the developer?
My three 'Longest past marriages' have:
dead husband/wife, measured to the subsequent death of the spouse; or
husband/wife with no death event, measured to the death of the spouse.
'Shortest past marriage' includes:
husband/wife with no death event, measured to the death of the spouse.
--
Martin

Hi, Martin!
Am Freitag, den 13.03.2009, 03:08 +1100 schrieb Martin Steer:
> Sorry, I should have said that I was using gramps31, via svn. Are you
> the developer?
I am the original Author of the Records report which has then been
incorporated into the 3.1 release. I know that there were some minor
changes done to my code before it was incorporated to make it compatible
with 3.1. However I would be suprised if these minor changes would cause
such a breakage.
> My three 'Longest past marriages' have:
>
> dead husband/wife, measured to the subsequent death of the spouse;
That would be wrong.
> or husband/wife with no death event, measured to the death of the
> spouse.
That would be correct.
> 'Shortest past marriage' includes:
>
> husband/wife with no death event, measured to the death of the spouse.
That would also be correct.
I just had a look at the code: this is what I used to find the earlier
of the death dates:
min(father_death_date, mother_death_date)
I assume this would still work with 3.1, can anybody confirm that?
Thanks,
Reinhard

On Thu, Mar 12, 2009 at 12:14 PM, Reinhard Müller <
reinhard.mueller@...> wrote:
> Hi, Martin!
>
> Am Freitag, den 13.03.2009, 03:08 +1100 schrieb Martin Steer:
> > Sorry, I should have said that I was using gramps31, via svn. Are you
> > the developer?
>
> I am the original Author of the Records report which has then been
> incorporated into the 3.1 release. I know that there were some minor
> changes done to my code before it was incorporated to make it compatible
> with 3.1. However I would be suprised if these minor changes would cause
> such a breakage.
>
> > My three 'Longest past marriages' have:
> >
> > dead husband/wife, measured to the subsequent death of the spouse;
>
> That would be wrong.
>
> > or husband/wife with no death event, measured to the death of the
> > spouse.
>
> That would be correct.
>
> > 'Shortest past marriage' includes:
> >
> > husband/wife with no death event, measured to the death of the spouse.
>
> That would also be correct.
>
> I just had a look at the code: this is what I used to find the earlier
> of the death dates:
> min(father_death_date, mother_death_date)
> I assume this would still work with 3.1, can anybody confirm that?
>
The code is here:
http://gramps.svn.sourceforge.net/viewvc/gramps/branches/gramps31/src/plugins/Records.py?revision=12001&view=markup
and the logic hasn't changed since Dec 2008.
This may be an artifact of not using fully-specified dates. That is, if a
death date of one spouse is "about 1968" then it may not be using that date.
If you change the variable REGULAR_DATES_ONLY from True to False, then it
will use all available dates. You can also fully specify a date (give month
and day, without approximation qualifiers) that will also work.
-Doug
>
> Thanks,
> Reinhard
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Gramps-users mailing list
> Gramps-users@...
> https://lists.sourceforge.net/lists/listinfo/gramps-users
>
>