On 2010/05/03 09:37, Ron Ferguson wrote: > Tony, > > I'm sorry, but in this case Legacy are correct. This is basic computing, if > you have files with the same file name in various directories just how do > you expect a machine to tell which is the correct one - it cannot see a > picture. You can't blame the operating system either because it also is > blind.
I have to agree with Ron and the developers. How on earth can this be a bug? How is Legacy (in its' present incarnation) supposed to know that because of *your* error it was supposed to use *this* picture and not *that* one? This always happens when you change something that affects Legacy behind its' back, and don't tell it what you've done. There is one way that Legacy could distinguish between two pictures, that because of lazy user practices, have the same name. The first time a picture is linked, an MD5 checksum of the file can be taken and stored in the database. Then, when looking for a similarly named file, the program can calculate the checksum of each file it finds, comparing it with the stored checksum. An exact match should mean that it has found the right picture - so far as it can tell! If no match is found, then a list of all similarly named files can be displayed, along with a thumbnail, and the user can then select the right one. -- Regards, Mike Fry Johannesburg 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://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
