

I can’t tell people just what a blessing John Nairn’s application is. It took quite a while to correct all the issues introduced by the other programmes, but now my data is as secure as can be because GeditCom understands GEDCOM like no other software. I’ve tried MacFamilyTree, Family Tree Maker, Heredis, iFamily. Whose fault? Who knows? TMG used GEDCOM less than ideally.
#Geditcom ratings mac#
I moved from Windows to a Mac two years ago and transferred my data from The Master Genealogist to Reunion via GEDCOM. While other programs have more eye candy, GEDitCOM II is the one that gets the job done.īiggest Pro: Best Macintosh genealogy program for the purist who likes to keeps things clean and simpleīiggest Con: Non-standard tags for URL addresses and media With some knowledge of Python or AppleScript, it’s possible to add even more functionality. I’ve tried just about every genealogy program out there, and I’m so glad that I discovered GEDitCOM II six months ago. Periodic exporting of the GEDCOM to another program that does synchronize with online databases mostly resolves that issue. Do I wish it synchronized with FamilySearch or Ancestry? Yes, that would be nice but introduces additional complexity that risks corruption of the database. After exporting the GEDCOM, it’s necessary to do a mass “find and replace” to change these GEDCOM tags so that the importing program will find the media and URL addresses. One quirk is that GEDitCOM II uses non-standard tags to denote media and URL addresses.

#Geditcom ratings software#
When I export from GEDitCOM II, I’m confident that it produces a good GEDCOM file that transfers relatively easily to other software with a minimum of issues to clean up. This facilitates changes that might be impossible to do any other way. But it’s also possible to open GEDitCOM’s editor to make changes directly to the GEDCOM file. Normally, editing changes happen automatically in the background when one uses GEDitCOM II. What I especially like about GEDitCOM II is that it operates directly on the underlying GEDCOM file, which is really just a text document. GEDitCOM II links to an excellent on-line place advisor that makes it easy to add geographic places, up to five or more levels deep. Unlike some other Macintosh genealogy programs, the text size is completely adjustable, which makes it easy on the eyes. This is a Macintosh program that is not the flashiest on the market, but it is highly functional. By the way, when open, the Preferences window is not mentioned in the Window menu and moves to the background when another app moves to the front of GEDitCOM.GEDitCOM is now GEDitCOM II. I can't recall properly, but I noticed that the text of the main settings are hardly legible because the background shade is similar to the text color. What is strange is that bug also concerns the colors in the Editing tab of the Preference window, which also seem to be affected. It might correspond to the colors I had actually tried to change (tree chart colors in dark mode, but which ones ? Perhaps the first 4 ones? or #2 and 3?), but then again I'm not sure. I remember the blue to be very light and the text was white. From what I can remember, the colors of the default format window looked pretty much the same as the light blue (and pink?) used in the male/female tree outline text) on top of the dark column, but I am not sure. I should have attached screenshots but I forgot to do any when the bug happened. My previous message was not very precise indeed. Is there a way to do a 'clean' reset the preferences to factory settings? Because even if I reverted the colors to their original ones, the preference file might have been damaged, causing that bug. So perhaps those color glitches only happen if the user attempts to make any color changes. But I haven't checked whether it would happen again.Īs Tim, I also tried to make some changes to the GEDitCOM II colors prefs a few weeks ago. (I didn't touch the automatic mode in the system prefs.) I installed build 4 only recently, and noticed that bug only once. Quitting and relauching the app usually does the trick. I understand that it can be difficult for you to track that bug, but it doesn't prevent the use of GEDitCOM II.
