|
|
|
Forum Newbie
Group: Forum Members
Last Login: 8/17/2005 10:46:40 PM
Posts: 3,
Visits: 0
|
|
| Can anyone please advice how I can do the above in the Beta version? I'm getting confused :lol: Thanks
|
|
|
|
|
Famous Writer
  
Group: Customers
Last Login: 10/31/2009 1:39:55 PM
GenoPro Version: 2.0.1.6
Posts: 438,
Visits: 2,595
|
|
There is only option to view either date(s) or place. On a menu, select display-> category of your choice.
Maybe is this option to ask for (if already haven't been asked).
Display -> birth/death date and place...
I'm not sure if it is possible to configure custom tags to do the job...
- "εν οιδα οτι ουδεν οιδα" (Σωκρατησ) - "The only thing that I know is that I don't know anything" (Socrates)
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: 8/17/2005 10:46:40 PM
Posts: 3,
Visits: 0
|
|
| V.l.o. thanks for your reply. I couldn't find a way of doing this. I beleive it would be very useful to be able to display. Thanks. Al
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Yesterday @ 11:13:07 PM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,173
|
|
For Beta 14, there will be an option to define a user tag by concatening other tags. For instance you could define a tag:
The tag formatter would display the year of birth and year of death (if any) on one line, and the place of birth on a separate line.
See post marriage line display/label for details.
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: 8/17/2005 10:46:40 PM
Posts: 3,
Visits: 0
|
|
| Thank you for the information. I am using Ver 2b 12g. Afraid that I'm not realy familiar with Tags - as yet. Is it possible to create in the version that I have? Thank you. Al/
|
|
|
|
|
Forum Master
Group: Customers
Last Login: Today @ 6:10:29 AM
GenoPro Version: 2.0.1.6
Posts: 980,
Visits: 9,340
|
|
Will this tag editor be able to include conditional clauses?
I would like to display year of birth, but if not known then year of baptism (preferably the latter should be preceded by the character'<' to indicate it is not the exact date)
In many cases with early records the year of birth is not recorded so you have to guess the year of birth. Where 5 children are baptised on the same day it is obvious that most of them were born in a different year
Similarly the age, where a death is known, should be shown as > to indicate uncertainty
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Yesterday @ 11:13:07 PM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,173
|
|
Will this tag editor be able to include conditional clauses?
Yes indeed. This is a built-in feature of the tag formatter: If a value is empty, it goes to the next tag within the braces { }.
| {birth.place, birth.baptism.place, birth.comment #100} |
In this case, if the place of birth is empty (not defined), then the tag formatter will try to use the baptism place, and if that fails, it will use the birth comment. The #100 will limit the text to the first 100 characters.
There is also a more elaborated conditional branching "if...then...else..." however I have not yet completed the code for this. The format for conditional branching will look like:
{birth.place?1}{?1}Bap. {birth.baptism.place}{/1}
{birth.comment#100} |
This will read as follows "if birth.place" is empty, then goto to "?1", otherwise resume after "/1", and display the birth comment on a separate line. This example is bogus because the text "Bap. " will always be displayed regardless if the birth.baptism.place is empty. A better solution would be:
{birth.place?1}{?1}{?birth.baptism.place?2}Bap. {birth.baptism.place}{/1}
{?2}{birth.comment#100} |
The "?birth.baptism.place?2" will look at the content of birth.baptism.place without writing it and resume to "?2" if the value is empty. Again, I have not finalized the syntax but you get the idea.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Yesterday @ 11:13:07 PM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,173
|
|
|
|
|
|
Grand Master
Group: Customers
Last Login: Today @ 8:46:16 AM
GenoPro Version: 2.0.1.6
Posts: 1,347,
Visits: 6,680
|
|
May I suggest a slight revision of my proposed syntax:
instead of
| <FmtBirthInfo T="{0} [was born{1|2&z}][ in {2}]{1}[[ and {1&z}] was baptised{3}[ at {4}]]."/> |
use
| <FmtBirthInfo T="{0}[{1|2}: was born][{2}: in {2}]{1}[{3}:[{1}: and {1}] was baptised{3}[{4}: at {4}]]."/> |
i.e. the field(s) to be tested appears at the start of the [...] construct and is terminated by a : (or similar) but is not part of the output string. This does away with the requirement for the field(s) to be tested to be first in the expression and also the need for &z encoding.
Also the addition of a not ! operator may be useful or even just for completeness.
(other readers will need to refer to Sample Report #3 to understand the above.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|