Search the Community
Showing results for tags 'persistance'.
Hey Andrew, I just did a clean install of OS X Mavericks 10.9.1 and did a fresh clean install of Alfred 2.1.1, too (no workflows, plain fresh and clean), and whenever I try to change a setting or import any skin, on next launch the setting is reset and the skin is gone I have tried repairing disk permissions with no luck, then tried changing the permissions myself with no luck either, then tried enabling sync and set to sync in non-dropbox folder then in dropbox and none worked either I can't do anything without Alfred, so what is happening? Could it be that Alfred is not fully compatible with Mavericks? After trying to "debug" the problem, I noticed the several things: 1. inside the "Alfred.alfredpreferences" package, the file "prefs.plist" found in ./preferences/appearance/options correctly shows that "hidehat=true" & "hidecog=true", which means the settings are persisted 2. however, as soon as I quit and relaunch Alfred, both the hat & cog are visible again, even though the previously mentioned file still shows "hidehat=true" & "hidecog=true", which means that Alfred is not reading the settings it just saved even though the settings are correct in the files on disk.. 3. next test: importing a skin; after importing any skin, it gets saved to the "prefs.plist" found in ./preferences/appearance of the "Alfred.alfredpreferences" package, and gets applied right away 4. but, after half a minute or so upon applying the theme, when I open alfred the theme has changed to the default and inside Alfred's preferences window the theme is gone, even though it still shows up in the previously mentioned "prefs.plist", which means again that Alfred doesn't read its own settings after it persists them?? So the conclusion is this: Alfred saves every setting I make, every change I make, but as soon as I quit/relaunch it all settings from disk are completely ignored. Why isn't Alfred reading the settings it saved? Maybe it's related to Maverick's new & more aggressive preference caching?? Because if a clean Alfred installation on a clean Mavericks installation doesn't work, then it's clearly that Alfred isn't Mavericks-ready yet... I really need Alfred to work, because I refuse to see it become wasted money P.S. while reading the forums, I noticed one other person say this exact phrase: "It seems as though Alfred was saving the settings to that location, but then not reading them back from there." - this confirms that Alfred is not reading back the settings it saves on Mavericks