Oops :) Turns out I was supposed to be setting
Cursor.setNotificationUri(...) in my ContentProvider. My bad.
On Thu, Mar 24, 2011 at 12:10 PM, Pete Doyle <petedo...@gmail.com> wrote:
> Just wanted to report an issue I'm seeing in CursorLoader with the
> Android Compatibility Package r1 (on a Droid / 2.2).
>
> Basically, it doesn't seem to be receiving calls internally to
> ContentObserver.onChange(), so it doesn't reload its data on a change.
>
> I was able to make things work by adding a call to
> Cursor.setNotificationUri(...) in
> CursorLoader.registerContentObserver():
>
> Before:
> void registerContentObserver(Cursor cursor, ContentObserver observer) {
> cursor.registerContentObserver(mObserver);
> }
>
> After:
> void registerContentObserver(Cursor cursor, ContentObserver observer) {
> cursor.setNotificationUri( getContext().getContentResolver(), mUri );
> cursor.registerContentObserver(mObserver);
> }
>
> Not sure if its really a bug, or if there's something wrong in my code
> that this change covers up. Thanks again for releasing the
> compatibility package, I'm really excited to be able to use Fragments
> and Loaders in my app.
>
> Thanks,
> Pete
>
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
