You should use the data provider, this will trigger a refresh of the
list view automatically.
On Tue, Jul 8, 2008 at 4:26 PM, Disco Stu 010 <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I see...Is this to make the behavior more consistent?
>
> If it gets deprecated, then when a Cursor is being used as a
Hi,
I see...Is this to make the behavior more consistent?
If it gets deprecated, then when a Cursor is being used as a
ListAdapter and an entry needs to be deleted, would we take the
following steps?
1. Issue a delete() to the DataProvider with the appropriate URL and
the relevant paramet
Hi,
Cursor.deleteRow() will be deprecated in or removed from the next SDK.
On Tue, Jul 8, 2008 at 4:10 PM, Disco Stu 010 <[EMAIL PROTECTED]> wrote:
>
> Hey Mark,
>
> Thanks again. I had reached the same conclusion as you that
> Cursor.deleteRow() should result in a DataProvider.delete with some
Hey Mark,
Thanks again. I had reached the same conclusion as you that
Cursor.deleteRow() should result in a DataProvider.delete with some
URI. However, I dont see that happening. I added a Log.w statement to
query(), insert(), delete() and update() methods of the data provider
and only q
> Mark Murphy, any thoughts? :)
Thanks for the vote of confidence! Though, bear in mind, I'm not an
Android team member, nor do I play one on TV.
> Now, according to the documentation, deleteRow is supposed to delete a
> row "from the underlying datastore". How does the Cursor know what
> tabl
5 matches
Mail list logo
