Whoops. I read "required" where you had "requeried". A managed cursor will re-run the query on the main application thread. I do not know of a way around that, other than to have the Cursor not be managed.
On Thu, Dec 9, 2010 at 8:27 AM, Mark Murphy <[email protected]> wrote: > You do not need to manage all cursors, regardless of thread. Managing > a SQLiteCursor may not be a bad idea, but it is not required. > > On Thu, Dec 9, 2010 at 2:39 AM, Jonas Schwertfeger > <[email protected]> wrote: >> From looking at Activity's source code it seems like managed cursors >> are requiered straight from the UI thread. Am I reading this wrong or >> is this indeed the case? >> >> -Jonas >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to [email protected] >> 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 >> > > > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.9 > Available! > -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.9 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] 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
