There have been a number of suggestions for the Wish List recently, with
some overlap, so I thought I'd quickly summarise them, and comment on them.
It may seem like a long list, but most of them are not new.
(1) Configurable columns on the Records Window. Pretty high up the Wish
List. Several requests for this. Brian Teece asked to be able to sort the
Records Window by given name. Adding Given Name as a separate column wld
allow this (if you add a column you wld be able to sort on it).
(2) Ability to move boxes in diagrams. Several requests. Unlikely to make
it into 2.1. There are alternative ways of addressing this problem using
the 'Avoid Page Boundaries' techniques, and repositioning diagrams on page
etc. However, I accept that this is still wanted.
(3) Jane Taubman wanted the ability to display Places in short or long
format. Is a good idea. Will look at that.
(4) John Sayer wanted to be able to print a tree as a vertical list (ie.
'Outline Descendant Tree' ), for easy posting to other people. Simon Dawson
also wanted an 'Outline Ancestor Tree'. Both of these will be part of the
reports deliverables included in 2.1.
(5) John Sayer. repeated a previous request to have expansion boxes between
all boxes/persons for even more pruning options. I presume that what you
want, John, is to be able to selectively weed out certain spouses while
showing others (for display purposes I mean, within a given tree diagram),
and/or weed out certain siblings while leaving others? Because you can
prune out pretty well everything else. Have I got that right? If I do this
one (which I am not averse to doing, but probably not for 2.1), I'd
probably do it by adding the option to hide boxes to the context menu that
appears when you right click on a box; so as not to clutter diagrams too
(6) Customisable Autosave.
(7) Automatic backup on exit.
(8). Option to remember window layout and GEDCOM being worked on when
next opening program i.e. 'take up where you left off'.
(9). Alphanumeric key jumping to paricular individual should respond to
multiple keys typed in rapid succession e.g. DAW would jump to DAWSON,
ignoring DARCY and DAVIES. This will be part of 2.1.
(10). Automatic entering of data into the 'count' fields so that they
automatically show the number of children, spouses etc. This one has come
up before. In my view what you want really is 2 things (a) the ability to
store as a separate of item of information the no. of children/spouses if
you know it (b) the ability to see the number of children/spouses that you
have actually recorded. And of course, these are not nec. the same.
(11) 'Replace' button to complement the 'search' button. That's
high on the list. I'd like it to get into 2.1 but there's a lot of stuff so
on the 2.1 list, so I don't absolutely guarantee it.
(12). Simon Dawson said he wanted a marriage end date (i.e. divorce date).
Obviously you can enter a
divorce event now (and its date). Do you mean that you want this on the
main page of the Property Dialog, Simon?
(13). Option to display surnames capitalized in Records Window main list.
If you click on Tools/Report Window options, and then uncheck "Display
Individuals Surname First in Main List" the names will be listed with given
name first and surname in caps. Is that adequate? Or wld you like to be
able to have surname first and in caps?
(14) Mouse click on Field title to produce help bubble about that field.
You should be able to get more help on fields its true.
(15). Multi-step undo and Redo buttons. That's been on my list for a long
time. Can't see it making it into 2.1 though.
The following weren't raised as wish list items as such, but are relevant to
recent discussions on the Mailing List (and are either already on the wish
list, or were put there by me following the discussions):
(16) It wld be nice to have a new query type for Events and Attributes (i.e.
each row returned represents a particular event or attribute, rather than a
particular record). Some of the things people have wanted to do would work
better with such a query.
(17) I've already mentioned this one in an earlier mail. Shld be able to
have wildcards in query expressions - e.g. find me anyone who has ever been
resident in Edinburgh (ie. any residence event). Or - find me anyone who
has Edinburgh included as part of the place of any event or attribute in
(18) The best solution to Simon Dawson's problem of a 'family' where the
father wasn't part of the family group, would be to make it possible to
specify that a 'couple' were either never-married, or even (as in this case)
never-a-couple. You could then specify in a diagram that you didn't want
'never-a-couple' types to be included in spouse lists. Or perhaps you could
show them but with a distinctive line to indicate that they had no
relationship as such. Of course, this wouldn't distinguish between the
parents from the child's point-of-view. Perhaps you also need to be able to
distinguish the case where someone is a mere genetic parent, and took no
active role in parenting. I see this kind of approach as the way forward in
List Administrator and Family Historian designer