Family Tree Maker(TM) Warts
Trees
Problems with the various kinds of trees in FTM.
 
Topics
All-in-one
Ancestor
Descendant
Fan
General
Hourglass
ODT
Vertical Ancestor
 

All-in-One Trees

 
  1. newThe All-in-One Tree takes so long to format that the FTM tactic of "format first, then allow user to make changes" becomes a barrier to use. For a file with just a few thousand individuals, the initial use may take up to an hour to format. FTM needs a way for the user to set the number of generations prior to formatting.

Ancestor Trees

 
  1. green starYou can change the typeface and size and lots of other things on Ancestor Tree Report pages, but you cannot change the page number font or size. If you are using reduced size pages, this becomes a problem, as the page numbers are stuck at a very tiny size, relative to everything else.
6.0
  1. FTM's penchant for abbreviation causes problems. Initial conditions:
    1. Preferences: Titles (Mr., Mrs., &c null)
    2. Add and select: "John \\ de Sutton, Lord of Dudley Castle"
    3. Title: Sir
    4. Ancestor Tree
    5. Items to include: Name only
    6. LAST, First Middle
    7. Mr./Mrs.
    8. Last name all CAPS
    9. No word wrap
    10. Font: Verdana, 8 pts
    Now, depending on the maximum box size, the name will change:
    Box
    width:
    Displayed name:
    2.8 (in.) Sir John de Sutton, Lord of Dudley Castle
    2.5 Sir J. de Sutton, Lord of Dudley Castle
    2.25 Sir de Sutton, Lord of Dudley Castle
    2.20 Sir
    Incredibly, with over two inches of space available in the box, FTM abbreviated the name right out of existence, leaving only the title!
I think that most people would be happy with simple truncation on the right rather than fancy — and failed — attempts at abbreviation. 

Just to show that this is not a typo!Sir
 
 

 

  1. Presentation: One item that can be included in each box is "Line in box", which places a horizontal rule at that position. When combined with the option to include siblings of the primary individual, the siblings are presented in one box separated by horizontal rules — the same style rule. The result is a confusing mess. The rule separating siblings should be of heavier weight than "Line in box", and extend to the vertical box boundaries.
  2. Number of Generations: Version 4.4 increased the maximum number of generations representable in an Ancestor Treeto 99. Since one key element one may want to include in an Ancestor Tree is the Standard, or Ahnentafel number of each individual, and indeed, there is such an option. To permit formatting such trees piecemeal, there is a companion option to set the starting number for the tree. Unfortunately, when they increased the number of generations to 99, the space to enter the starting number was left at 6 places,  meaning that the highest starting number is 999,999, which is an individual in the 19th generation. Therefore, one cannot start a numbered tree with individuals in generations 19-99.

 
 

Showing confusion from using same rule for two purposesconfusing mess
 
 
 
 
 
 
 
 

Slot for entering starting Ahnentafel numberspace to enter

  1. newText alignment: Centered or right aligned text is poorly placed in the tree boxes. All boxes in the same column are made the same width, but text in the boxes is aligned as if each box were only as wide as its longest line. Boxes with only a single line of text thus will always display that text left aligned. In the example, all text is supposed to be right aligned.

 
 

poor text placementexample


Descendant Trees

 
  1. Single Line: Secondary spouses are erroneously shown when Direct Descendants option chosen. [See also ]
  2. Single Line: Formatting a descendant tree from an ancestor to one specific descendant will leave out the spouse of the target descendant. All spouses, including unrelated second or third spouses, of everyone except the target descendant are included.

Secondary spouse Who is This should not be displayederroneously shown
[McE]
exampleleave out
  1. newSingle Line: (V6) Spouses of siblings are shown, if the Include Siblings option is selected. 
  2. newName formatting: (V6) The new option of including the a/k/a in the name splits the name in the wrong place in the towline format. Choosing the name format First Middle "aka"\\Last (put surname on second line) prints as First Middle\\"aka" Last (split before a/k/a).
forum messageSingle Line

forum messageName formatting


Fan Trees

 

General Tree Problems

 
  1. Presentation: Box background color extends beyond border in certain border styles. 
  2. Options, format: One can choose which fields to display in a tree and, optionally, the source for particular included fields. The fields can be displayed in a font and size of your choice, but the source is always shown in the same font/size as the field to which it refers. 
  3. Options, format: Multiple fields may be selected by SHIFT-click or CTL-click, and attributes of the selected fields changed together. Changing font in this way also usually resets bold style to normal.
Picky, picky, but such detail is important for that professional appearanceextends beyond border
 
It should be possible to make the citation more easily distinguishable from the data.
 
  1. Dates: The date form "birth-death", available in the various sorts of tree, uses a format that makes certain dates too easy to misunderstand. The dash used to separate the birth date from the death date is the same as the dash used to separate two dates in a date range. The use of different size dashes would make the meaning much clearer: e.g. "1901-1902 — 1903". 
Showing how two different dates look very much alikemisunderstand

Hourglass Trees

 
  1. Formatting: Failure to center an hour glass tree and overlaying of goto arrows on the first line of the first page of the tree. 
Showing how long name in title causes double-wide formattingDetails
[EGG]
  1. newFormatting: Under some conditions Off-page Connector (GoTo) boxes are placed requiring crossed or crooked connector lines
  2. newFormatting: Placement of the top row of boxes is not adjusted to accommodate the Title. Setting the title in 48 or 72 point type will cause it to overlap the boxes of the first generation. The descenders of lower case letters will interfere at even smaller type sizes.
screenshotcrossed or crooked

ODT

Outline Descendant Tree
 
  1. Automatic titles, generated from the primary subject's name, will not wrap to a second line. Particularly long names will cause formatting problems:
    • Two sheet wide formatting 
    • Typeface size reductions for entire report
  2. When using the option "Direct Descendants Only" from a "Secondary Individual", individuals in the result who have additional spouses not involved in the specific descent line chosen will cause spurious output to appear at the bottom of the report: "2nd wife of Xyz". That's it; no 2nd wife is listed (nor should she be)—just this trash line. [see also ]

 

Showing how long name in title causes double-wide formattingformatting
 
 

Note the trash lines at the bottom of this reportspurious output

  1. green starAn A/K/A, if present, will be used for additional spouses.
6.0
[McE]
  1. One of the options is to Include Spouse's Mother and Spouse's Father. The resulting ODT can then be used to exportthepersons included in the tree, but spouse's parents will not be exported. [See also ].
Include individuals Father/Mother in ODToptions 
Export individuals in ODTexport

Vertical Ancestor Tree

new
 
  1. Touted as a "new feature" in V6, the same effect can be obtained with an Hourglass Tree specified with only one descendant generation.

My colophon
3505
Access counter
© 1999 Roderic A. Davis, 2nd
All Rights Reserved
Link to home pagePlease
visit my home page!
  APR1999
27JUN1999
"Family Tree Maker" is a trademark of Brøderbund® Software, Inc.
Neither this site nor its author have any connection with The Family Tree Maker program or its owner. Advice and suggestions offered here are to be used at your own risk. Your mileage may vary. Batteries not included.
[TOP]
Email:dav4is@yahoo.com
Snail:
Roderic A. Davis, 2nd
P.O. Box 118
Hyde Park, NY 12538
USA
Click to receive email 
when this page changes
• Powered by NetMind•

1