I think this is your code here:
$MyCursorHelper$MyContentObserver.onChange(CursorTreeAdapter.java:503)
Looks like when you switching between activities and multiple data
population tasks are going on, they have conflicting Cursor state in
your onChange method. You might want to use a static fla
This is how I start the query in my viewing activity.
mRoutes = managedQuery(getIntent().getData(), ROUTE_PROJECTION, null,
null);
This is some of the provider code.
public Cursor query(Uri url, String[] projection, String selection,
String[] selectionArgs, String sort)
...
Cursor c
I use managedQuery to start a managed cursor. That accomplishes the
same thing right?
On Apr 21, 5:44 pm, "Megha Joshi" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> If you call Activity's startManagingCursor() method, it should
> automatically take care of the cursor based on Activity's lifecycle. You
Hi,
If you call Activity's startManagingCursor() method, it should
automatically take care of the cursor based on Activity's lifecycle. You can
look at the NotePad tutorial for example. You could also provide your
relevant code here to help us debug it further?
Thanks,
Megha
On Mon, Apr 21,
4 matches
Mail list logo