|
|
|
|
Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: Tuesday, October 28, 2025
Posts: 4,886,
Visits: 22,799
|
Beta 16 will have this built-in. New methods will be added to the GenoDate to extract the "type" of date, whatever it is a full date, partial date, an estimate date and other date types.
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 2 days ago @ 9:23 PM
Posts: 3,464,
Visits: 26,854
|
The idea was to capture Gedcom date modifiers such as ABT, BEF, AFT, EST, CAL etc. I.e. type of approximate date. I know this area has beeen covered elsewhere in the forum and is a planned enchancement to GenoPro.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: Tuesday, October 28, 2025
Posts: 4,886,
Visits: 22,799
|
From the attachment you sent, I see what you mean. This is a though decision I made to have the "date" as a standalone object. In other words, once you have "i.birth.date", you have an atomic datatype, and there is no more a link to the original source. Since there is no intrinsic methor or property named "type" to the GenoDate, you get this error.
What you can do is change your user-defined tag from "birth.date.type" to "birth.date_type" which will work.
By the way, I am curious, what values do you enter in "birth.date.type"? Maybe this could be a built-in feature of the date object (for Beta 16)...
|
|
|
|
|
Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: Tuesday, October 28, 2025
Posts: 4,886,
Visits: 22,799
|
Can you send me a sample .gno file producing the error. I will take a look at the issue and fix it.
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 2 days ago @ 9:23 PM
Posts: 3,464,
Visits: 26,854
|
My initial attempts at using the new report generator were unsuccessful because I kept hitting the following error:Generating report to G:\Shared Documents\ Family\Genealogy\reports\
Cloning document Masterb13...
Opening configuration file Config.xml for skin '\_English - Generic Report'...
Loading dictionary.xml...
Processing template 'init.htm'...
Processing template 'default.htm'...
Processing template 'toc_families.htm'...
Processing template 'toc_individuals.htm'...
Error at line 72: Object doesn't support this action: 'i.birth.date. year'
Microsoft VBScript runtime error 800A01BD
After a bit of head scratching I realized that one of my custom tags, used to record the original Gedcom date qualifier, which I had called 'birth.date.type' was causing a problem with the GenoDate object. When I deleted the custom tag, using the tag editor, and saved the file the problem remained, even though the tag had been removed from the .xml file. It was only after I re-imported the .xml file into GenoPro that the report was produced without error. It was as if the erroneous tag remained in the .gno file even after deleting it with the tag editor. I submit this bug in case other users hit the same or similar problem. Perhaps a 'reserved word list' is required to prevent such clashes.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|