|
|
|
Famous Writer
      
Group: Customers
Last Login: Today @ 6:09:04 AM
GenoPro Version: 2.0.1.6
Posts: 314,
Visits: 1,950
|
|
| Ron, Excellent job on the Kinship Calculator, but I have found an occasion where a little error checking may be required. In the case where first cousins marry: 
if you run the kinship calculator on the husband and wife the result is, as expected: 
However, if you break the link between Father (W) and the grandparents, the result is: 
whereas it should indicate no blood relationship. The result is the same for any husband and wife unrelated by blood.
|
|
|
|
|
Grand Master
      
Group: Customers
Last Login: Today @ 5:48:22 AM
GenoPro Version: 2.0.1.6
Posts: 1,174,
Visits: 5,584
|
|
Isn't the definition of 'in-law' 'related by marriage' ? The script does attempt to show in-laws as well as blood relations but would be better here if it said 'partner of'. I'll change that in he revision I am working on.It is proving difficult at the moment to show all possible relationships for some pairings where their paths cross higher up the tree, so for now it will just show the 1st one discovered.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Grand Master
      
Group: Customers
Last Login: Today @ 5:48:22 AM
GenoPro Version: 2.0.1.6
Posts: 1,174,
Visits: 5,584
|
|
| Time for an update, although probably not the last. If have now added an HTML report providing a lineage, or pedigree, chart of the relationship including each generation along the way.The updated skin is attached to the 1st post in this thread as usual. A sample report however is attached to this post.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Forum Master
      
Group: Customers
Last Login: Today @ 4:52:59 AM
GenoPro Version: 2.0.1.6
Posts: 843,
Visits: 7,663
|
|
|
|
|
|
Grand Master
      
Group: Customers
Last Login: Today @ 5:48:22 AM
GenoPro Version: 2.0.1.6
Posts: 1,174,
Visits: 5,584
|
|
Don't know what happened there, I could have sworn that I had updated the attachment, but then it disappeared. Perhaps it was too late in the day. Any how, I've put it back now.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Famous Writer
      
Group: Customers
Last Login: Today @ 6:09:04 AM
GenoPro Version: 2.0.1.6
Posts: 314,
Visits: 1,950
|
|
| Ron, there is a gender problem on the new report when selecting in-laws. For the following family: 
running the report on the highlighted individuals results in this report: 
|
|
|
|
|
Forum Master
      
Group: Customers
Last Login: 2 days ago @ 11:38:49 PM
GenoPro Version: 2.0.1.6
Posts: 726,
Visits: 6,096
|
|
Ron, the section "KinshipChild" needs to be redone. A "son" in German is "Sohn", however a "grandson" is called "Enkel", which means the word son is not carried on, but the word "Enkel" with the Prefix "ur" for "great" grandson. The same goes for "daughter". How can I reduce the space in the upper section between the header and the next two phrases? How can I reduce the font in the squares in the lower section, below the common ancestors?
update: solved the font problem, thanks
|
|
|
|
|
Famous Writer
      
Group: Customers
Last Login: 12/16/2008 8:50:03 AM
GenoPro Version: 2.0.1.6
Posts: 477,
Visits: 1,271
|
|
Ron, I think it is quite a complexe subject you tackled, with so many options/depth of pedigree links and relations. Even in my own FR language, I don't even know how some particular links or relations are called, when the links/relations are too deep! Unfortunately, this may prevent me of doing a full proper FR translation. Pity. In the meantime, I noticed the following: - when two husbands (of the same F) are selected, the script wrongly says: Husb1 is a partner of Husb2. I think the <KinshipNotRelated> ph should rather be used/shown. - when, say, one of the selected Ind is a 'divorced Husb or Wife', should the script says 'was' instead of 'is' whatever relation?Despite, I suppose, that you're not focusing on the translations facility yet, I anticipate the requirement for the following F gender provisions: - a <KinshipCousin_F> - a <KinshipCousin1_F> - a <KinshipGreatGrand_F> - a <KinshipHalf_F> - a <KinshipInLaw_F> - a <KinshipPartner_F> - a <KinshipPerson_F> - a <KinshipUnion_F> The above ph could be replaced by provision of gender ID as {params}. JC
|
|
|
| | |