Mark Murphy wrote:
[...]
> If you're sure your data set won't be a-changin' underneath you, you 
> could try using an unmanaged cursor. However, if other activities have 
> the capability of modifying the data you're showing in the list (e.g., 
> it's a public content provider), then I suspect you *want* to requery 
> upon the activity restarting, lest you show stale data to the user.

Yup, switching to an unmanaged cursor fixed it. I also checked that my
ListView automatically notices when my database update thread modifies
the database; that still works, so manually requerying is obviously
unnecessary.

Thanks!

Romain Guy wrote:
>> On a related note, with a ListActivity, is it my responsibility to save
>> > the selected item in the icicle on freeze and restore it on thaw, or
>> > will the ListActivity do it for me?
> 
> Not in post-M5 SDKs :)
> 
> A lot of work went into ListView's state saving after M5 so you might
> want to wait until the next public release of the SDK before trying to
> work around this issue as it is probably handled for you already.

Fair enough. I'll wait for the next SDK before tackling the freeze/thaw
issue; hopefully the problem will just go away!

-- 
┌─── dg@cowlark.com ───── http://www.cowlark.com ─────
│ "I have always wished for my computer to be as easy to use as my
│ telephone; my wish has come true because I can no longer figure out
│ how to use my telephone." --- Bjarne Stroustrup

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to