GRAMPS 2.0.3 ("Mynd you, møøse bites Kan be pretty nasti..") released
The GRAMPS project is terribly embarrassed to have to release the 2.0.3
release within hours of the 2.0.2 release :-) A last minute change in
2.0.2 ended up causing a bug that prevented dates from being properly
The entire difference between 2.0.2 and 2.0.3 are two pairs of
parentheses. Unfortunately, these are important parentheses.
Version 2.0.3 -- the "Mynd you, møøse bites Kan be pretty nasti..." release
* Fixed Date handler bug that would not allow dates to be updated.
Thanks for all the good work, but I've got a couple of bugs to report here.
I'm using 2.0.3-1 on Debian, and I'm adding in parents to a person in
the Family view.
1. My name is, surprise, Stoffel. The "Choose Parents" dialog seems
to default to _only_ showing males named Stoffel when I go to
choose the parents. This is annoying, since the person who's
parent's I'm adding is named "Gaunt" as a last (Family) name.
I have NOT selected "Show All" here, but I would think that I
wouldn't have to, the selection should be narrowed to the Family
name of the Active person who's parent's we're choosing, ney?
2. When I *do* add a new male person using the Plus button, they _do_
get added, but they are not selected in the "Choose Parents"
window, nor is the "Show all" checkbox ticked. So it's not obvious
whether or not the person has been successfully added. I now have
two entries for that same person.
But when I add in a mother, I get to choose from among all females
(who I assume are *older* than the Active Person) without a
But this time, when compared to 2.0.1-2, they do get added correctly
as parents, so things are looking up.
I found another interesting issue when editing a person using the
"Edit Person" dialog. When you enter a birth date and hit the Tab
key, the selection is advanced to the "Invoke Date Editor" button
(which had turned from Red to Green). I then hit "enter" and a
dialog box pops up for a tenth of a second and goes away. At this
point I can move the mouse, but I can't enter any data, nor do any of
the tabs at the top change either.
It took a while, but hitting the "Escape" key gets me back. So there
must be something strange going on here. Let me know if I can give
you any more details.
I don't get any traceback errors that I can see related to this,
thought I've got some others that I'm trying to track down and figure
out where they come from.
Thanks again for Gramps, it's a good tool to use. Here's a semi
simple feature request:
When you run Tools -> Utilities -> Verify the Database and get back
the report, it would be really nice if for each problem reported,
there was an ability to click on the person/family/child and edit them
to apply any fixes in real time.
Once any changes are made, you could enable a button called "Re-Verify
DB" so people could check their fixes and that no other problems have
Also, the default width for the box that does popup is too narrow, I
think it should match the width of the main Gramps window, otherwise
you end up scrolling back and forth a lot to see what's happening.
It would be also nice to sort the report into groups of warnings, such
as "Large Age Differnces", "Old Marriages", "Long Widowhood", etc.
[Sorry, John, for using your message for hanging this rant on, I have
wanted to write about this for some time, your message just reminded
me of it. And sorry for sending this to you twice, I think Iid not
copy the list the first time.]
> I'd personally prefer for the family name of kids to be filled in all
> the time when adding, if the default chosen by gramps is wrong, it's
> not hard to fix.
For what is worth, in at least some cultures using two surnames and
where women keep their maiden names, a good default may be the
mother's surnames reversed, a practice that was frequently used to
hide the fact that the father was not known.
It is just a data point, nothing more. We are sort of used to the
lack of support. If there has to be one default, it makes sense that
it is one that suits the majority. Most software handles poorly our
double-surname naming system and genealogy software is not the
exception (even GEDCOM hardly supports it). As a consequence, non
compatible abuses of the format are seen (there is eben a popular
adaptation of PhpGedView around that implements one such abuse).
Another area where cultural clashes make users abuse the GEDCOM format
is place names: we do not explode place names like you (a sequence
separated by commas). We do it like this: 'San Julián (Ferrol, A
Coruña, Spain)'. Since genealogy software presumes that the GEDCOM
string is useable in reports, people will write place names in a
format that is not conforming with the GEDCOM specification. That
creates data portability problems and makes standardized place name
parsing impossible. But users are not to blame for this: they just
make do with what they are given and will settle for proper output
over GEDCOM conformance everytime. Most of them could not care less
about the latter even if they knew it existed.
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r _______________________________________________
Gramps-devel mailing list
[hidden email] https://lists.sourceforge.net/lists/listinfo/gramps-devel