-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLOSED] If you open an older version of Brackets, it resets some of your preferences #3013
Comments
Comment by redmunds
|
Comment by TomMalbran I'll look into it. It would be possible to delete the old preferences only once, on the first upgrade, but leave them on the second time it tries to move the preferences. Shouldn't be that bad, since mostly only developers keep switching between older and new versions and not many users do. Although this is a problem only if you go to Brackets versions older than 22, so on the next sprint switching between the current version and the GitHub one, won't be a problem. |
Comment by TomMalbran I was able to reproduce this issue once following the same steps, but not again after that time. Could it be that the preference ID changed for the recent projects in my last Preferences ID request? |
Comment by pthiess
|
Comment by peterflynn Removing Sprint 22 milestone per above note. Issue is already mentioned in release notes. |
Comment by pthiess
|
Comment by redmunds This was added to Release Notes. Closing. |
Issue by peterflynn
Thursday Mar 21, 2013 at 22:56 GMT
Originally opened as adobe/brackets#3207
Result: Recent Projects dropdown contains the project you opened in step 4, the default Getting Started, and nothing else
Expected: Preferences from latest version are unharmed
This seems like a bit of an edge case, since it's unlikely to be running old builds after upgrading (except perhaps for Edge Code, but that uses a separate prefs store). However, it's still a little worrisome... might be worth pondering for a min before this sprint closes down.
The text was updated successfully, but these errors were encountered: