It has to be me that is causing the problems.Genealogy apps should always follow the GEDCOM standard, right? You’d be justified in thinking that if you’ve read many of my articles, and generally speaking, apps should follow the standard, especially 5.5.1, since GEDCOM 5.5 is obsolete. (Contrast the adverse comments about the developers of one of the other major programs who, according to one reviewer, had “even gone to the length of contacting me regarding negative feedback on third party sites and telling me that the program simply MUST work. The developer, John Nairn, is very responsive to requests for help or to suggestions for future changes. Other programs use Gedcom but often adapt it in ways that hinder the transfer of information to other users: GEDitCOM even provides ways to correct these idiosyncracies. But underneath it all is a rock-solid base built on the Gedcom standard. You can use it “out of the box” and it will do pretty much anything you want you can tweak it a little using the inbuilt customization options or by fairly simple editing of the formats to suit your particular needs or your preferences about how it looks or if you’re more adventurous you can make major changes. Since then each revision has added a further swathe of improvements. When GEDitCOM II came out my comment on another review site was “the best just got a whole lot better”. I checked back on the others from time to time and never saw anything to make me change. When I started working on our family tree I tried most of the genealogy programs available for the Mac but it didn’t take a lot of thought to settle on GEDitCOM. Various minor improvements, including improvements in provided browser styles and extensions.All GEDitCOM II drag and drop features were updated to current methods (which may have fixed drag and drop issues seen in some recent MacOS versions). MacOS has revised the way applications should implement drag and drop features.A work around was found that now appears to get around that bug. High Sierra has some bugs in split pane windows (such as some window with notes in one pane and rest of the record in another pane).If GEDitCOM II fails to read a GEDCOM file claimed to have UTF8 encoding (because it has an encoding error), it now tries alternate reading methods and displays message that extra methods were tried.The POIs now work (but are no longer customizable by users). Icons for points of interest on maps are now stored on, becuase High Sierra refuses to load locally stored icons in Google maps.
0 Comments
Leave a Reply. |