|
By Howard53 - Friday, December 1, 2006
|
|
This has been around since the option was introduced to use approximate dates of birth and death in the Genogram, but I have only just noticed that the approximation indicator (~) is omitted in the index and the narrative parts of the report, whereas the SVG reflects the original Genogram - see highlighted points below: 
Would it be possible to include the ~ within the report?
|
|
By GenoProSupport - Friday, December 1, 2006
|
|
At this point of releasing GenoPro 2.0, it is very risky to make a modification which may cause a bug somewhere else. Ron is the expert regarding the report generator. If he feels comfortable making the change and the impacts are not too significant, then this improvement is a big welcome.
|
|
By genome - Friday, December 1, 2006
|
I have not shown approximate dates as yet because I am not aware of any Report Generator property or method for extracting such dates. I have just done a bit of experimenting and the only way I can find to extract an such approximate dates is to use Individual.TagValue("Birth.Date") as check the result. But I wonder if there any built-in methods available? The .ToString(<format> ) method only seems to work for a full date, i.e. with day, month and year present. I have found that the only viable method to check or format dates is ToStringNarrative that formats the date as per the control panel. If there are no built in methods then yes I can provide some code without too much effort or risk that will check for approximate dates and report accordingly.
|
|
By GenoProSupport - Friday, December 1, 2006
|
|
Future updates will include more properties and methods to format dates. At the moment, I don't think there is a way to output the approximation symbol.
|
|
By Howard53 - Wednesday, December 6, 2006
|
Well done : :: v2b20d has the solution for 3 out of the 4 highlighted:
The only missing one is the Ancestor Pedigree Chart, but that is less important.
|
|
By idrisi333 - Thursday, December 7, 2006
|
Why did the report generator that?
In the program I use only one ~ !
|
|
By bogistad - Friday, December 8, 2006
|
|
There is a problem with approximate dates where the exact birth date is known and the date of death is approximated. As an example: Date of Birth: 7 Mar 1779 Date of Death: >1826 The report prints "He died at the age of 47 after 1826." Obviously, there is no way of knowing how old he was when he died as the date of death is approximated. I would suggest that the age not be calculated/printed if any date is an apoproximation.
|
|
By genome - Friday, December 8, 2006
|
|
Why did the report generator that?
It does look a bit strange. Are you using a customised report skin? The standard skin only shows year of birth whereas your example has some full dates hence I assume a custom skin is being used. The repeated approximation symbol may be due to a problem with the Date.ToString method. However I cannot explain the doubling of dates. Can you give more details of your customisation? I would suggest that the age not be calculated/printed if any date is an apoproximation. I agree. I had missed this issue. I will tweak the report to exclude age at death if date of birth or death are approximated.
|
|
By idrisi333 - Friday, December 8, 2006
|
Thanks Ron.
I used this symbol "~" before 20d too. When I make a new file whit 20d and use the ~ the report is good. But if I use my original file which cointains ~ symbols the report looks like in the picture.
I used the original skin.
There is one of my files:
http://palmai.uw.hu/test_1.gno
|
|
By genome - Friday, December 8, 2006
|
|
Thanks for the sample. It had me foxed for a while. However the problem is a custom tag, birth.DATE.COMM, in your file. This seems to upset GenoPro's Report Generator methods for dates such that both Birth.Date.Approximation and Birth.Date.Year return ~~<date>. The work-around is to delete this custom tag. Use Table View / Individuals, then right click on column headed birth.DATE.COMM and select the 'X Delete custom tag birth.DATE.COMM' option. If you need to retain this information I suggest you rename the tag to say birth.DATE_COMM for example, using GenoPro's Tag Editor.
|
|
By Prydwyn - Friday, December 8, 2006
|
|
I know this is nothing to do with reports, but I think it is relevant to the topic... I do find it slightly annoying that when you use an approximate date with the '~' option, or if you use the '>' or '<' before a date, it is not shown on the genomap. It will ignore the approxiamtion and take the numeric value as an absolute. Is there (or will there be) any way of having the approximations be displayed in the genomap? Thanks, John
|
|
By appleshaw - Saturday, December 9, 2006
|
|
Which version are you using? If you look at an earlier post on this topic you will see ~ on a GenoMap
|
|
By Prydwyn - Saturday, December 9, 2006
|
|
I have always been using the latest version, ususally within one or two days of it being released. For example, I've just downloaded b20e. I create a new male, and set his birth to '~1801' and death to '~1852'. The genomap displays '1801-1852' over the square symbol, and in the symbol it says '51' (Age at death, when I would like it to read '~1801-~1852' and '~51'. Cheers, John
|
|
By appleshaw - Saturday, December 9, 2006
|
Sorry, I did not read your original posting properly. You are referring to the Genomap, not the svg copy in a report.
At present I think the answer lies in using a Custom Tag - of the sort generated by Ron's Utils. However in a recent posting he said these need to be updated because of the renaming of several GenoPro tags.
|
|
By Howard53 - Saturday, December 9, 2006
|
|
Prydwyn (12/9/2006)
The genomap displays '1801-1852' over the square symbol, and in the symbol it says '51' (Age at death, when I would like it to read '~1801-~1852' and '~51'.This occurs when you have the Display menu setting on 'Year of Birth and Year of Death'. This may be a bug (it also occurs on 'Year of Birth and Year of Death + ID). If you have the Display menu set to any of the other date settings the ~ symbol is shown. There is probably a lack of space to show the ~ within the gender symbol.
|
|
By idrisi333 - Saturday, December 9, 2006
|
Thanks Ron.
I deleted the column. Now it works properly...
|