dd644c179c1bf47d82d776d7f644e4fc1467159d |
|
10-Oct-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Fallback to SharedPreferences$Editor.commit() when no apply() exists. Gingerbread widened the SharedPreferences.Editor interface, adding an apply() method. Most people don't implement this interface themselves, but a couple apps do. A few spots in the core framework take a SharedPreferences[.Editor] from apps, which might be a pre-Gingerbread implementation without an apply() method. This patch makes sure we never depend on the presence of an apply() method, falling back to commit() if apply() isn't available. Change-Id: I32693ac9227a60b694526a26a30234fb17a40581
/frameworks/base/core/java/android/preference/Preference.java
|
66fce5068a8a3aeb28aaf713843891b286a75280 |
|
31-Aug-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
Renaming SharedPreferences$Editor.startCommit to apply Also removes the artifical restriction that only one apply() can be in flight at once. That was old from when I thought it'd end up being required, but wasn't. Change-Id: I3540ea8be6e0760d6a51d218186f71655c2f3f55
/frameworks/base/core/java/android/preference/Preference.java
|
333b8cba996c8ebb8ca55ebfc5cc536bdd64af94 |
|
26-Aug-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
SharedPreferences$Editor.startCommit() Adds a fire-and-forget save method (startCommit) to the SharedPreferences.Editor, which is the way most people use it anyway. This commit adds the implementation. The previous commit added the interface and docs: previous change: Idf9934b445da1fb72b79f0192218b47c0a7f5a34 git commit: edf32d01316bd3432c023f17747461b08ae36375 In addition, this change: -- adds a generic "runPendingWorkFinishers" mechanism to ActivityThread to wait on async operations that are still in flight and use it for this. -- ties runPendingWorkFinishers into Activity.onPause, BroadcastReceiver, and Service. -- makes sSharedPreferences keyed on name, not File, to avoid unnnecessary allocations -- documents and guarantees what thread OnSharedPreferenceChangeListener callbacks run on -- makes a few things in frameworks/base use startCommit(), notably Preference.java (which was ignoring the return value anyway) Change-Id: I1c8db60ad45643226fe6d246d3e513eeb7bd0ebd
/frameworks/base/core/java/android/preference/Preference.java
|
a98129b9110371aa036d8fcf23fff709595b16ff |
|
06-Oct-2009 |
Amith Yamasani <yamasani@google.com> |
Fix preference caching to increase recycling of preference views. Add extra safety measures - no recycling of derived preferences as they may override onCreateView or getView
/frameworks/base/core/java/android/preference/Preference.java
|
bae6fc244732476d6e6b565e64518e1beafd66c6 |
|
30-Sep-2009 |
Amith Yamasani <yamasani@google.com> |
Fix for 2155255: Revert "Cache inflated view to avoid inflation of layouts in preferences" This introduces problems when scrolling through preference screens, due to a clash in this cache versus the ListView's cache. This reverts commit 01dbc2ed55a081d41d233e891ea1ea1b0484f383.
/frameworks/base/core/java/android/preference/Preference.java
|
01dbc2ed55a081d41d233e891ea1ea1b0484f383 |
|
28-Sep-2009 |
Suchi Amalapurapu <asuchitra@google.com> |
Cache inflated view to avoid inflation of layouts in preferences If layout id is specified for a Preference object, convertView is set to null in its adapter which results in inflation of Preference view in getView each time the Preference object is laid out on the screen. Just use an instance variable to cache the inflated view nulling it whenever the layout changes and use it in initing the convertView in getView.
/frameworks/base/core/java/android/preference/Preference.java
|
0bb9960598067f3320cdae8ab42c1ba0f3376f21 |
|
08-Sep-2009 |
Tammo Spalink <tammo@google.com> |
Do not die when printing empty prefs. Addresses issue: http://buganizer/issue?id=1974140 Change-Id: I0001d69e8d278d4ca900f5ce56ad50c0b4b6b694
/frameworks/base/core/java/android/preference/Preference.java
|
da53eca79e02ac70761c379f9f2cb3babce9e79d |
|
28-Mar-2009 |
Michael Chan <> |
AI 143298: am: CL 143150 Fixed the problem where setEnabled(false) has no effect from onResume(). The problem was that the Preference widget was reenabled when its dependency was in enabled state. The enabled field was basically overloaded. The fix was to add an additional field to keep track of whether its dependencies were met. Original author: chanm Merged from: //branches/donutburger/... Automated import of CL 143298
/frameworks/base/core/java/android/preference/Preference.java
|
9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/preference/Preference.java
|
d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/preference/Preference.java
|
15ab3eae2ec3d73b3e8aa60b33ae41445bf83f4b |
|
20-Feb-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@132569
/frameworks/base/core/java/android/preference/Preference.java
|
f013e1afd1e68af5e3b868c26a653bbfb39538f8 |
|
18-Dec-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Code drop from //branches/cupcake/...@124589
/frameworks/base/core/java/android/preference/Preference.java
|
54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/preference/Preference.java
|