On Wed, Nov 19, 2008 at 8:55 AM, Eric B <[EMAIL PROTECTED]> wrote: > What I'm taking from this is that if my BroadcastReceiver, which runs > off an AlarmManager, is accessing the preferences and the user then > opens the PreferenceActivity in a separate process the behavior is > undefined and most likely causes the PreferenceActivity to not "find" > the existing values?
I would recommend not using the same shared preferences across multiple processes at this point. > I guess I'll have to switch to a database implementation then. > SharedPreferences don't seem very robust, I'm not sure I can ever use > them again, which is really sad since they are quite easy to use. You can use them any time you are not accessing them from multiple processes, which applies to the vast majority of applications. If you are actually setting up your application to run in multiple processes, then lots of things get more difficult, and this is one of them. -- Dianne Hackborn [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
