Hi
I'd like to use an sqlite database in my m4a project and I discovered
sqlite-net which seems a nice wrapper. However, since I need guid datatypes,
I cannot use the last published version on nuget, so I downloaded the very
latest version from git and managed to compile it for my pc based client.
I have a complex class and need to save state when activity/fragment is
destroyed and recreated.
I want to avoid using Parcelable if possible. Is this the best alternative
in terms of simplicity and performance? I couldn't think of any other way
to do it without leaving files/objects behind that
On Feb 4, 2013, at 11:20 PM, craig wrote:
> I have a complex class and need to save state when activity/fragment is
> destroyed and recreated.
>
> Is this the best alternative in terms of simplicity and performance?
_Some_ form of serialization is sane, whether that be binary, XML, JSON, or
wh
I considered a static variable.
If Android kills my process then the static variable would be gone but the
serialized variable would be retained right? That's the only reason I'm
leaning towards serialized.
I guess to clarify my question, is serializing the class and *then packing
the serialized
