QUOTE(david_dl @ Jul 8 2006, 02:38)

The .cfg files were not designed to be shared, apart from privacy issues there are other issues, such as references to non-existant files, drives and audio devices which could all cause major problems.
I know, but it's still the easiest way to share complete layouts. And there are not major problems but only minor. I tell ppl what settings in preferences they'll have to take care of (with my fb2k it's only media library paths, foo_uie_explorer, foo_playlist_bind, none of them would cause problems). And of course at very first they'll have to change the audio driver setting.
QUOTE(bhoar @ Jul 8 2006, 06:57)

1) Add a foobar2000.prv file, to be used for private storage.
2) Add encrypt/decrypt functions that uses something unique to the user account or windows installation as the key or hash-seed, in order to hide the private items.
From the concept 1) is a bad idea, as, if you have user_profiles_enabled, configurations somewhere under %appdata% are supposed to be private. 2) is a typical solution, but probably support intensive ("my fb2k does no more work after i reinstalled windows!!!11!")
I wish there was a "export configuration file" function which strips out all sensitive data, mru, whatever, but theres one problem: foobar2000 cannot decide about sensitive data which have been stored by 3rd party plugins.