I am using Legacy Version: 8.0.0.473 & I have the same "cancel" dilemma & I can reproduce it anywhere.
Clicking the Cancel button takes you back to the Individual's Information Screen - click that Cancel - I had assumed, that this Cancel button on the Individual's Information Screen eliminated ALL changes you just made for that person. WRONG. It left the Event as it was* -* "saved by Cancel button *"* Anne On Fri, Aug 28, 2015 at 4:40 PM, Brian L. Lightfoot < [email protected]> 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 accidently 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 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
