Family Historian User Group

I would love to be able to change an event using a drop down list. For example, I have many people who have the 'Resident' event attributed to them but I have now found out how to make a new event, ie. Living with Parents, and I want to change all 'resident' events to Living with Parents, where appropriate.

Another example; from a census, I thought someone was resident at an address, only to find that they were working as a servant at that address and not resident. So to be able to change the event to occuplation would be good, rather than having to create a whole new event and delete the old one.

ID:3540

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

I'm not sure this is a good idea. If you have customised events etc how will FH know where the data is supposed to go when you change the event? A residential attribute isn't really much like an occupation attribute, although they may have some common data. Are we trying to get FH to be too clever?

Re your point about the Census, my understanding was that anyone who was at the address on the relevant night was listed at that address. Servants were usually resident and didn't come in on a daily basis. Therefore working at the address meant that they resided there. It might be different if it was a large estate where there was separate servant accommodation, apart from the main house.

Gerry

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 by the user being prompted for the extra data (event->attribute) or moving the attribute's detail to a local note. It is true that a residence is not the same as an occupation, but rather than the programmer trying to double guess what is valid and what isn't its best to leave it to the user.