Family Historian User Group

The marriage template for a family is wrong. It should not use {individual} but {couple} instead. However the bug still exists since the template for divorce is '{couple} were divorced {date} {place}' and this is always displayed as the template and never as the sentence. So I would consider this (a...

To view the link you need to select the submitter record in question in the record window, then select View->Record Links... In the record type selection ensure it is set to all or individual. If you set the record type to submitter it won't show any records since there won't be any submitters linke...

I've checked with a simple two person one source file and marriage sources are removed with the 'Exclude' option selected in the export function. I would consider this a bug with a relatively high priority since it causes unexpected data loss. Technically it could be said that sources to a family re...

I wish to make a request that V4 should handle the multiple occurrence of TEXT fields in SOUR records in more user friendly manner than just dropping them. It is standard practise throughout all other programs that when change occurs that the upgrade handles any specifics to make the old data work w...

The fact that the auto-source indicator is easily missed is due to FH failing one of the basic UI design guidelines. According to Jeff Johnson's book 'GUI Bloopers - Don'ts and Do's for Software Developers and Web Designers' this is blooper #47 Easily Missed Information. He says that developers ofte...

Nick Walker said: OK so not everyone can write their own software, but if I did write it I'd make it available to others and I'm sure other programmers, like yourself, would do the same. I am in fact in the process of doing this. ;-) And though I might be critical of FH I will still use it compared...

Agree too that the reminder needs to be more prominent, though I would vote for a non-flashing indicator and placed where you eye normally focuses, ie. on the property window somewhere. An alternative would be to have the background colour change in some way when auto-source is on.

There will always be differences between programs but if they generally present the data the same way, that's one big thinking step that's not necessary. For instance spreadsheets all use the same format for showing the data, the same for word processors. If a word processor showed the text as a ser...

Nick Walker said: The important thing is that with Family Historian if one day you do feel that it has been left behind, it will be fairly straightforward to transfer your records to another program, the code isn't locked into some impenetrable format. No it easy to view your data and transfer most...

I agree that here keeping up with the Jones in the case of the Focus Window. For any user who has changed to using FH, there would be quite a bit of a culture change to cope with the record and diagram views when they would have been using a family type view of their data. Now new users can delve st...

It looks like I will be getting loads of these exception reports when I upgrade. I have been using multiple TEXTs in source records to hold separate pieces of text (e.g emails from a contact). I agree that FH4 should report an exception about multiple TEXT fields (especially as I was one who reporte...

I would also add that the thread that is doing the background processing should be of a lower priority than it currently is so that it doesn't put so much load on the CPU nor make it difficult to use other programs. I hope that it doesn't make thumbnails EVERY time you start the program. Even with a...

I've reported a similar scrolling problem with the scroll tab jumping back to the top at certain points when dragging it. My issue was with the reports, but it could be the same code being used in the thumbnail view. Does the behaviour change when you change the size of FH's window? This is what I r...

redynstruc said: (remember how much easier it was to 'reveal codes' with Word Perfect than it is trying to get Word to realize that you really do want to edit the style tag which is, regrettably, 'inside' of your selection?). You'll love this article about formatting codes then - http://www.codingh...

Curt, you are right that the Gedcom 5.5 spec requires duplicate entries of file references if an object is used a number of times. It does this already with place names (a more likely candidate for multiple entries). This does not follow good database design guidelines - however Gedcom is not a data...

Once you have viewed an image you can't change it's type via the property dialog (not even in the all tab) as FH brings up the message 'Can't change format. Object in use'. However you can change it's type/format in the record window at any point in time. Another way is to not view the image, or alt...

One thing to think about when looking at the birth place from censuses is to think of the census as a source not an event. So if you have multiple sources (marriage and death for example) with differing birth dates, think about how you would record this and then use the census data as just another e...

Curt, I have a very 'in progress' program which will solve your images problem. I've sent you the location of my program privately. The reason you have this issue is because FH does not follow the Gedcom spec 100%. The gedcom spec specifies that objects which have filenames are specified using the O...

You shouldn't have any problem with the Gedcom files. The standard hasn't changed since v2.3. The difference between the two versions might mean that you will have to re-enter some settings so make sure you note down your preferences in v2.3 before you install v4. I suspect uninstalling v2.3 is bett...

Half way through April and still no news on when V4 will be delivered. We haven't even been treated to a few grainy screen shots to keep up the anticipation level. I do hope that the delay is due to logistical problems with resellers and such like and not due to last minute bugs in the software. ID:...

The pools show all people who are related by blood or marriage. It could also include all people who are related by being family friends, witnesses, servants, lodgers, etc. It should be an optional feature of the pool function. This request is linked with request 374 which requests more support for ...

I'm sure it was mentioned somewhere that attendants to a recent family history show (WDYTYA) saw some screenshots displayed by a retailer (not Calico Pie themselves). I don't know why we haven't been allowed to see any yet.

FH will have no problem in working out where to put the data when the event is changed. This is because all events follow the same structure. Basically all that's happening is that the type of event is being changed, not the data itself. As for changing between an event/attribute that can be handled...

See my request for an event rename feature - http://www.fhug.org.uk/wishlist/wldispl ... lwlref=352 which sounds very much like your request.

To be able to create a family by selecting two individuals in the record window and making them the husband and wife in a marriage. When two individuals are selected, the edit menu should have an option to create a family record. It would also be nice if the right click context menu would also have ...