You only need the XML file containing the PreferenceScreen if you want
to show an activity that is similar to the Android settings screen.
You'd have to subclass PreferenceActivity in that case and call
addPreferencesFromResource() in onCreate().
http://code.google.com/android/reference/android/pr
My issue was simpler than that. I was trying to get any setting to
read, write, save, then recall under any condition. What I was doing
wrong was I didn't have the xml file set up right. It appears to work
fine now.
Thanks, it was from studying your code that I figured out what was
wrong. So
If you do not store values with special characters in your settings,
it might be interesting to see some of your code in order to analyze
why you're losing them.
If we're only talking about the problem with special characters, you
should be fine with Base64 encoding values that potentially lead t
I've been struggling with these shared preferences. I want to save a
resolution setting, so that people with different degrees of vision
can see the screen. With a Diabetes application, this is a very
important feature.
What I've found thus far, however I cut the cake, I lose my settings
with e
Yeah, Base64 encoding would certainly help until the platform bug is fixed.
I guess a lot of people with strong passwords (i.e. passwords
containing special characters) are in trouble with a lot of apps right
now.
It's funny you mention two apps I share parts of the codebase with. I
stripped dow
This has been a recurring problem with K-9:
http://code.google.com/p/k9mail/issues/detail?id=143
and apparently the core Email as well:
http://www.androidforums.com/showthread.php?p=16842
and possibly other apps, too:
http://groups.google.com/group/android-developers/browse_thread/thread/5efd37a55
After removing "<" and ">" from the preferences I have not seen this
problem anymore.
Sorry, I don't know what else could cause your problems, Chander.
Christoph
On Sun, Jan 25, 2009 at 12:08 PM, android_soft wrote:
>
> I have noticed this behavior couple of times. But I have not been able
>
I have noticed this behavior couple of times. But I have not been able
to reproduce, also I do not have "<" or any other special character,
except some Double values encoded as Strings.
Chander
On Jan 25, 12:39 am, Christoph Studer wrote:
> Okay, so my current suspicion is that I got bitten
>
Okay, so my current suspicion is that I got bitten by
http://code.google.com/p/android/issues/detail?id=1707
I have one preference value containing "<" and ">" which are
improperly encoded due to above bug. My guess is that the XML parser
chokes on this value and the pref file is ignored. I think
9 matches
Mail list logo