Default review interval preferences not sticking
 

I originally sent this as feedback in August [B][OG #325829][/B], but I'm still seeing it in the 1.5 release candidate. I'm hoping it can get fixed before they wrap up this release.

It seems the "By default, review projects every..." setting under the Data preferences pane isn't being preserved between app launches. For example, if I set it to "months" and quit the app, when I launch the app and open the preferences again I see it set back to the default of "weeks".

The same problem exists with the numeric value: I set it to "4" and "weeks" (since 1 month doesn't stick), relaunch OmniFocus, and check the preference again and it's right back to the default "1 week" setting.

Essentially, it seems impossible to have a default review cycle of anything other than a week!

Anybody else able to reproduce this?

-Dennis

[QUOTE=Toadling;49380]

Anybody else able to reproduce this?

-Dennis[/QUOTE]

Me.

I'm on the latest build. 106053

It reverts back to 1 week upon relaunch for me too.

I set it to 2 days, quit, relaunched, and it went back to 1 week.

Reproduced on the latest latest build (106095) as well.

We think we have this fixed as of build 106165, so please let us know if you see any problems with it as of that build or later.

Looks good from here -- even remembers what I had set the default review interval to in my test! I'm guessing it would store the user's specified value, but never read it back from the plist file?

[QUOTE=whpalmer4;49439]Looks good from here -- even remembers what I had set the default review interval to in my test! I'm guessing it would store the user's specified value, but never read it back from the plist file?[/QUOTE]

Yes, I'm seeing the same thing. I wish now I had actually tested it further by creating some new projects. They probably would have had the proper default review interval even though the preference pane wasn't displaying the setting properly.

Well, no matter. Things seem to be working nicely now. Thanks, Omni Group!

-Dennis

I don't know the exact specifics, but it turns out it was in fact both storing and reading the value set in preferences, the preferences UI just wasn't reflecting it after restart.