So after “major surgery”, it is always important to do an initial check to see that everything is connected right. Often problems show up as program crashes due to accessing invalid memory locations. These are relatively easy problems to find, since the exact location of the error in the program can be determined, and the cause can be found by tracing the path leading to that point. The hard problems are the ones that don’t show up right away but lurk in the background and simply produce incorrect results. Some of those can be a real challenge to find and fix.
First bug: the old file information wouldn’t clear when a new file was loaded. This bug took 20 minutes to find and fix. The fix was simply 2 lines: 1. To clear the Behold file, and 2. reload the Organize Info from the cleared Behold file.
Here’s a strange one: After clearing, the 3rd GEDCOM entered does its autoorganize with the 2nd GEDCOM’s data. And the 4th does its with the 3rd’s data. This gets fixed when I add the code to delete the GEDCOM from the list of GEDCOM pages.
Deleting a GEDCOM causes a crash. The crash point was where the currently selected Family was changed if its GEDCOM was the one deleted. The crash occurred if there was no currently selected Family. It was simple to add another condition for this case.