Thanks Cathy...I tested that with a download to new file from Family Search Family Tree and it looks like the User-Defaults were applied. It may indeed help with new files but does not help with a change to a customization in one database that the user may expect will be effective in all the databases. Ron Taylor
On Wednesday, March 5, 2014 9:37 PM, Cathy Pinner <[email protected]> wrote: Hi Ron, This is already there for a new file (that's not a newly converted file but File > New File) provided you have saved user defaults. >From the Help: Whenever you start a new family file, Legacy looks to see if you have saved any user-default family file settings. Any that are found are saved in the new family file. If there are no user-defaults, the Legacy-defaults are used. Cathy At 06:48 AM 6/03/2014, you wrote: >As I said, the current version 8.0.0.412 can "Save ALL current >settings as User-Defaults" and then in the other databases "Reset to >User-Defaults". What I was proposing is a method that could >automatically apply the "Reset to User-Defaults" when a new database >is opened. But also a way to assure that all databases get the >latest User-Defaults should they be adjusted from time to >time...only if the user wishes that to happen. If the user wants >each database to have different (ff) settings, that is also possible >with the method that I outlined. >Ron Taylor > > >On Wednesday, March 5, 2014 10:00 AM, CE WOOD <[email protected]> wrote: >MARVELOUS IDEA! Please make a suggestion that they do this ASAP! > >For the many of us who need to produce reports now and are stuck >using Legacy 7.5 because we can get what we want today, it would >REALLY encourage us to start the learning curve on Legacy 8. As it >is now, we would have to keep both a Legacy 7.5 and a Legacy 8 fdb. >Big deterrent! > >If there were a way to set the user files are apply them to a new >database, I would start Legacy 8 in a heartbeat! > >But why bother when I must still use Legacy 7.5, because any time I >converted my latest 7.5 fdb to Legacy 8, I would have to go through >the onerous process of settings all my user settings! How many hours >are there in YOUR day? > > >CE > > > > From: [email protected] > > To: [email protected] > > Subject: Re: [LegacyUG] Customisation > > Date: Wed, 5 Mar 2014 16:39:03 +0200 > > > > On 05 Mar 2014 16:18, Ron Taylor wrote: > > > > > I had this same concern with Legacy 8 customization. The (ff) > settings do make > > > sense for multiple databases. The problem is that Legacy > assumes that "Reset to > > > Legacy-Defaults" should be used when opening a database for the > first time in > > > Legacy 8 versus "Reset to User-Defaults". Once the database has > been opened, > > > the (ff) settings are established and work fine from that point > forward. A > > > simple question "Would you like to apply User-Default > customization settings to > > > this database?" might be asked when a database is opened the > first time in > > > version 8. I think it also happens when a new database is > started. That way, > > > the user who assumes all the (ff) settings will be functional > in every database > > > that is opened will have that condition. It is assumed that the > (gbl) settings > > > will be used in every database for the user. > > > > The problem here is that the first time a NEW file opened, there are no > > user-defined FF settings for the file. You'd need to be able to > save the FF > > settings from a file as a named set that can then be applied to a > new file - NOT > > AN EXISTING FILE! > > > > This way, you could have multiple FF sets to select from when a > new file is created. > > > > -- > > Regards, > > Mike Fry > > Johannesburg (g) > > >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 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
