westmeadboy wrote: > Seems a bit weird to me. For example, if you are maintaining a cursor > pool (and so do not know how a given cursor is being used), you need > to be careful about which thread you call close() on.
Get rid of the "cursor pool", then. What problem are you trying to solve by leaving multiple Cursors open? -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Training in NYC: 4-6 June 2010: http://guruloft.com -- 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 To unsubscribe, reply using "remove me" as the subject.
