2011/1/28 Bob2000 <denbigh1974@boltblue.com>

Bob2000 wrote:
> I'm using 3.2.4-1. My choice of page size doesn't seem to affect this
> issue.
> I've just tried an earlier back up of my tree and found that it produces
> an SVG file with no problems.
> So the Family descendant report doesn't like my more recent, bigger tree.
> When I use the 'check database' tool on it, everything seems ok.
> Groan...Anybody with a similar problem?

I've narrowed the problem down to one long marriage place name (66
characters, including spaces). If I remove this place name, the problem goes

[I found the problem by creating the report for successive generations. Then
when I found which generation caused the problem, I narrowed it down to the
family by running the report for each family.

When I looked at the PDF output for this family, I saw that the marriage
place was corrupted.]

Conclusion: Family Descendant Tree add-on can't handle long marriage place

Please post a bug ticket for this on the bug tracker.
Normal solution to those kind of problems is to ellipsize long names (long name...) or to word wrap on a fixed length.


It's still an excellent add-on though, in my opinion.
View this message in context: http://gramps.1791082.n4.nabble.com/Family-Descendant-Tree-add-on-tp3048751p3244219.html
Sent from the GRAMPS - User mailing list archive at Nabble.com.

Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
Gramps-users mailing list