What is “merging”?
MacMAME is clever about clones. If you have a parent ROM set (a zip file containing all the ROM files from the parent game) and you want to play a clone, then the clone’s ROM set will only need to contain the ROM files unique to that clone (MacMAME will look in the parent ROM set for the ROM files which are identical to the parent’s). This saves disk space on your computer, since identical ROM files aren’t duplicated. Some web sites distribute clone ROM sets this way, containing only the ROM files which are different. The drawback of this approach is that you’ll need a copy of the parent ROM files in order to play the clone, which is why many web sites distribute clones as complete sets so that they can be played without needing the parent set. Another approach is to have one zip file which contains all the ROM files for the parent game and all of its clones. This is called a “merged ROM set”, and if you’re a completist who likes to have as many ROM sets as you can, it can be more conv
Merging is the process in which two ancestral records become one. Every ancestral record that you put into OneGreatFamily is matched against all records from other members. Each record is dealt with individually in the merging process as OneGreatFamily compares names, places, dates and other valid information to determine the likelihood of any two records being duplicates. OneGreatFamily even compares family records, as they are saved separately from individual records. After any records are merged, any differences in their information become conflicts. (For example: If your record had a birth date of 1588 and the other of 1589, you would see 1589 displayed as a conflict.) When duplicate (or very similar) records are found, they are automatically merged. This is indicated by an exclamation mark in Starfield™. When two records are found to be similar, but not similar enough to be automatically merged, a hint is created. A hint is displayed as a light bulb in Starfield™ and signifies a p
