Thanks for pointing out that other danger. The thing about the Cancel not working is that if you realize you replaced the event content with the clipboard contents, then saw you had the wrong info in the clipboard, you click on CANCEL --- but here is the danger you pointed out --- the event window immediately closes. And you have no way of knowing that the wrong info was pasted. Then you start doing backups as Jenny suggested. But unfortunately your backups now contain the wrong info. You’d never realize it until by chance you happen to be looking at that event at some time in the future and think “This info doesn’t belong with this person/family.” You then check your backups and they are all wrong.
Now back in the real world, once you hit CANCEL because you realize you have the wrong info on the clipboard, you would typically reload the clipboard with the correct info, then re-open that event, and then replace the contents with the correct info from the clipboard. This works as expected especially if you are replacing a Census event with an updated Census event. But the danger comes if you accidently opened something else such as a Military Event and replaced it with the clipboard census event of a Census event. The data from that Military Event is gone forever from your current database. As Jenny said, this is where a backup would save the day but you’d better hope your backup includes the Military event that was erased. And you better hope that you noticed the event was replaced because you don’t see the erroneous replacement and the only info you have that something went wrong would be the name of the event got changed in the individual’s list of events. I wonder how long this bug has been around? Did somebody say it can also happen in v7.5? Brian in CA I also just noticed that I can’t spell “doesn’t” correctly in the Subject line. J Apparently MS Outlook doesn’t do spell check on the Subject line. Another bug. From: Ana [mailto:[email protected]] Sent: Monday, August 31, 2015 6:54 AM To: [email protected] Subject: Re: [LegacyUG] Possible Bug - Cancel does't cancel Good morning Jenny. I do lots of backups but I can't say I do one every time I do some editing. Until Brian L., pointed this out - I just didn't realize the default to "not cancel" and wonder if I ever got in a hurry & didn't do a back-check on all I had just recorded OR meant not to record, as the case maybe. I guess time will tell. Thanks Brian. On Mon, Aug 31, 2015 at 8:11 AM, Jenny M Benson <[email protected]> wrote: On 28/08/2015 21:40, Brian L. Lightfoot wrote: > 10. There is no going back so whatever data you had in the event that got > replaced are gone forever. That's why you always do a backup before performing any action that cannot be reversed. (Or perhaps you don't!!) -- Jenny M Benson Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
