Another reason that in SOME areas Legacy is really the best software!! Jay
On Tue, May 21, 2013 at 12:00 PM, Brian L. Lightfoot < [email protected]> wrote: > Aha. As I now understand it, these .lcs files are provided as "starting > points" which can also allow users to edit their skins as freely as > possible. And changing or overwriting any or all of these .lcs files will > never affect the user from merely clicking the DEFAULT button to return to > the original install state. Somehow, I was thinking that the "original.lcs" > file was the default setting but as I found out, changing and overwriting > that original.lcs file still allows a user to bail-out of everything by > clicking on the DEFAULT button and return back to the install state. > > OK, nice idea. Besides providing skins, Legacy allows editing of the skins > and the provision to save those edits. Something I never realized but then > I always liked the default settings just fine. :-) > > > Brian in California > > -----Original Message----- > From: Sherry/Support [mailto:[email protected]] > Sent: Tuesday, May 21, 2013 10:15 AM > To: [email protected] > Subject: Re: [LegacyUG] Saving Personal Settings > > if you don't click on the "Save" in the lower right corner after you've > created your own Color Scheme, then you won't be able to get it back if you > try something different. Some people like to vary their interface. > > If you edit one of the Color Schemes that's already there (click on Load > to access them) and save with a different file name, you won't overwrite > the existing Color Scheme. As always, if you use the same file name for the > Color Scheme, you'll overwrite the one supplied by Legacy. > > I wish more programs would allow editing of their skins! I have one > program that I like a color choice to a point and wish I could edit it a > bit! > > > Sincerely, > Sherry > Technical Support > Legacy Family Tree > > > On Tue, May 21, 2013 at 10:03 AM, Brian L. Lightfoot < > [email protected]> wrote: > > But clicking on the SAVE button is not necessary to implement the > change. That particular SAVE button is only to create or modify a color > scheme that you may wish to recall at a future time. If a user makes a > change on the color screen, he can then click on CLOSE, and then the main > customization window comes back up where the user can click on SAVE the > customization settings which would include any of the previously made color > changes without affecting the .lcs files. > > > > If the SAVE button on the Color Change window is NOT clicked, the color > changes are still stored in the Legacy.usr file. All of the original .lcs > files remain unchanged. A user can re-install Legacy and get back all of > their color changes by using the previously saved Legacy.usr file. > > > > Now, back to that particular SAVE button on the color change window. If > the user clicks that, they can save all their color settings in one color > scheme file or surprisingly, modify one of the original .lcs files. I > always thought this was a bit dangerous to allow the user to modify an > original color scheme file until I noticed another button, DEFAULT. As a > test, I modified one of the original .lcs files by SAVING it, overwriting > the original. But then by clicking DEFAULT, I was able to get all the > colors to return to their original settings. So apparently the default > settings are NOT stored in the .lcs files. > > > > But then back to my original observation, if the color settings are also > stored in the Legacy.usr file, why bother with a user created .lcs file? > Aren't they redundant? > > > > 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
