One final point. I had 2 or 3 emails from some users saying that their SAVE and CANCEL work as expected. My original post was about using the clipboard to replace one event with another, not with directly editing one event. So in other words, everyone can continue to open any event, type gibberish into the NOTES field and hit CANCEL. Your original event remains untarnished. But be careful about using the clipboard on replacing the contents of events. CANCEL doesn't work in that case and there is the potential to irrevocably lose data. Because of that, I should think this bug report gets priority attention and will be fixed in the next update.
Brian in CA PS - I have no idea on how this bug effects SHARED EVENTS. I don't use SHARED EVENTS so maybe somebody might want to see if they can break the program using them. -----Original Message----- From: Brian/Support [mailto:[email protected]] Sent: Saturday, August 29, 2015 8:42 AM To: [email protected] Subject: Re: [LegacyUG] Possible Bug - Cancel does't cancel Confirmed. Problem report raised to have this fixed. Brian Customer Support Millennia Corporation [email protected] http://www.LegacyFamilyTree.com On 28/08/2015 4:40 PM, Brian L. Lightfoot wrote: > I can't remember if this has been discussed but I noticed this problem > several weeks ago and today I took the time to reproduce it and document it. > > First of all, don't try this on your family database file. You will > lose data! Use only a test copy of your file or the sample.fdb files. > > It all has to do with copying an event from the clipboard to overwrite > another event typically on another individual when you want to > completely replace the terminology of the notes or maybe more info from a > census event. > Doesn't really matter because this will happen to any type of event > even if you accidentally click on an existing Military event when you > have a census event in the clipboard. > > Here are the steps. > 1. Open any event from any individual. > 2. Click on the left icon towards the bottom right which signifies > "Copy Event to Clipboard". > 3. Close that event. You now have one event on the clipboard. > 4. Open up any other event on that same person or on any other person. > 5. Click on the right icon towards the bottom right which signifies > "Paste Event from Clipboard". > 6. Legacy will open a window entitled "Replace Contents?" Click Yes. > 7. At this point let's pretend you've had one too many beers to drink > or you just realized you had the wrong other person opened, or the > wrong other event. Or whatever.you made a mistake. > 8. Normally you would click on SAVE to save the contents of the event > but since you made a mistake, you click on CANCEL. > 9. Guess what? Cancel did nothing and the contents of the event were > saved after all. > 10. There is no going back so whatever data you had in the event that got > replaced are gone forever. > > I should think cancel means cancel and save means save. But apparently > as the code is written right now, once you agree to replace the > contents, even before you see it pasted in place, it's a done deal. > Events are saved even before you click on save. There is no such thing as > CANCEL. > > Am I missing something here or do I see this needing a little code clean up. > > Brian in CA 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
