I accept that point and I think quite a few people have already made that clear. I never used that feature because my personal preference is to use only the unspecified source for a new person. Then later changes are updated with other sources for the detailed events. So, when I saw it was an issue for several very knowledgeable people on this list, I simply asked the question. Jerry / www.MerriamFamilyTree.org
Ron Bernier <[email protected]> wrote: >And why should the programmers make changes to the way the program functions >just to accommodate those who can not/will not take the time to fully read the >help files and tool tips? Others have made it very clear that they fully >understood how that function works. I really wish people would stop >requesting changes to dumb down a program (any program) just so they do not >have to think about what they are doing. This suggestion completely ignores >those folks who have made it very clear that they know how to properly use the >function and use it regularly. > >Ron Bernier > >________________________________________ >From: Mike Fry [[email protected]] >Sent: Wednesday, July 27, 2011 7:44 AM >To: [email protected] >Subject: [LegacyUG] Misusing The Source Clipboard [Was: Using Source Clipboard] > >On 2011/07/27 01:10, Jerry wrote: > >> Since that 3-bar icon is not liked and not intuitive, why wouldn't the >> programmers consider changing it for a future update? Sounds like other >> people will continue to have the same issue, whether new to Legacy or not. > >I suppose it's just about feasible that things could be arranged so that it >could only be used once and only then on a new person. > >Create the new person and fill in all the details you have from the first >source >- along with events :-) Set up the source clipboard. Light the blue touch-paper >and stand back and watch! Thereafter, the button becomes disabled for that >person. For other people where the button has not been used, it can be disabled >once a first source has been assigned to that person. > >Requires a small change to the database, but Legacy does this quite often. When >the change is first used on a file, the program can run through the file >disabling the button on all individuals and marriages that have at least one >source. > >-- >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 >Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on >our blog (http://news.LegacyFamilyTree.com). >To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > >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 >Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on >our blog (http://news.LegacyFamilyTree.com). >To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > 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 Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
