By crash893 - Wednesday, August 9, 2006
|
When i put a marriage as annulled i get this in the report (minor but still a bug)
Rodney Keith and unkown were married. Their marriage was annulledThey were divorced. They have a son and a daughter, named Chris and Amy.
Male Chris
Female Amy
also in the tree with 2b17
when i put the couple as divorced i no longer get the // through the marriage line
|
By Howard53 - Thursday, August 10, 2006
|
crash893 (8/9/2006) also in the tree with 2b17
when i put the couple as divorced i no longer get the // through the marriage line
I am using 2b17i and the divorce line (and the other Relation lines) are displaying correctly.
|
By GenoProSupport - Thursday, August 10, 2006
|
You need to explicitly pick the Divorce relationship to display the // on the family tree. The Unions dialog documents the events but has no effect on the display.
|
By crash893 - Sunday, August 13, 2006
|
why not
if they are divorced they are divorced
why do i need to mark it in multiable spots
what about the space issue?
|
By jcguasp - Monday, August 14, 2006
|
The following phrase “PhDivorce”, to my opinion, is actually not finished:
<!-- 0=marriage annulment, 1=divorce date, 2=divorce place, 3=divorce requested by --> <PhDivorce T="{  }[{?0}Their marriage was annulled][{?!0}They were divorced{1}{2h}][{?3}They were divorced]." /> |
because the 4 fields: “Requested by”, “Husband’s Attorney”, “Wife’s Attorney” and “Officiator / Agency” are presently not included/taken into account in the phrase. Or is it done on purpose? Same, of course, applies to the associated code line 193 of Lang.vbs. I suppose this is another wee job for Ron. I also agree that, as soon as something (the “Marriage Annulled” tick box or any/some of the other fields) has been input within the “Divorce” section, the connecting line and the “Relation” field on the Gene tab, should automatically update to a divorce (or also possibly Nullity) type union. In fact, I even suggest that this field “Relation”, if possible within the system, be totally interactive, based on the various input fields of the divorce section but also in case of one Ind dies, the Relation field should also auto-update from, say, a Legal Cohab into a Legal Cohab and Deceased.
|
By genome - Monday, August 14, 2006
|
Yes I had picked up on the original post from crash893 modified the phrase to <!-- 0=marriage annulment, 1=divorce date, 2=divorce place, 3=divorce requested by --> <PhDivorce T="{  }[{?0}Their marriage was annulled][{?!0}[{?1|2|3}They were divorced]]{1}{2h}[ at the request of {3}]." />
| ready for Beta 18 but I seem to have overlooked responding to the post. I'll take another look and include the attorneys and officiators/agencies. The relation field was perhaps originally intended for use when there was no marriage/divorce information present. I will look at the report a see if I can change it so that the family relationship line pattern reflects the state of the union if the relation field is blank. Perhaps Dan could add a check in Genopro and flag a warning when the relation value contradicts the 'union' status and also use the union status for the line when left blank. The 'union' object also needs to be extended to record relationship states other than marriage & divorce/annulment. e.g. dating, engagement, cohabitation etc. Maybe it could be extended to cover all 'family' events.
|
By jcguasp - Monday, August 14, 2006
|
Thanks Ron. Don't forget, in Lang.vbs, to remove <> "" at the very end of the parameters list, otherwise it says:
|
By jcguasp - Monday, August 14, 2006
|
Another small remark: when the option “Don’t Know” is selected, the narrative says:

I simply suggest to remove this option from the drop down list.
|
By King Semsem - Tuesday, August 15, 2006
|
Or change it to read "at the request of one of the two" or something like that.
|
By GenoProSupport - Friday, August 18, 2006
|
Ron (8/14/2006) Perhaps Dan could add a check in Genopro and flag a warning when the relation value contradicts the 'union' status and also use the union status for the line when left blank.GenoPro 3.0 will have a Problem Spotter to display warnings of potential errors such as the birth of a child before its parents, a child with more than two biological parents, divorce date prior marriage date, etc. I have added this suggestion to our Problem Spotter list.
|
By Satrek - Saturday, August 19, 2006
|
GenoPro 3.0
A bit off-topic, but I wonder, how are you planning to proceede - will 3.0 be the next full version, or will there be 2.1, 2.2 etc?
|
By genome - Monday, August 21, 2006
|
GenoProSupport (8/18/2006) GenoPro 3.0 will have a Problem Spotter to display warnings of potential errors such as the birth of a child before its parents, a child with more than two biological parents, divorce date prior marriage date, etc.Drifting off the original topic again but another one for the Problem spotter list is multiple pedgree links of the same type for an individual to the same family, particularly hidden ones spanning from one genomap to another to a hyperlink of that individual, as these cannot be seen without moving the hyperlinked individual back to the original genomap.
|
By GenoProSupport - Monday, August 21, 2006
|
Ron (8/21/2006) Drifting off the original topic again but another one for the Problem spotter list is multiple pedgree links of the same type for an individual to the same family, particularly hidden ones spanning from one genomap to another to a hyperlink of that individual, as these cannot be seen without moving the hyperlinked individual back to the original genomap.This is a great suggestion. I have added the following to the Problem Spotter: Find hidden objects such as overlapping pedigree links, family lines and individuals.
|