hello everyboday
thank you for your support and sorry for my slowly answer...
it works with a contentResolver and a ContentObserver (code).
do you mean that it isn't for the performance of the device not a good
idea to work with something like that?
thanks in advance
public class
I was just explaining why we designed things the way we did.
On Tue, Dec 9, 2008 at 8:25 AM, jaspher [EMAIL PROTECTED] wrote:
hello everyboday
thank you for your support and sorry for my slowly answer...
it works with a contentResolver and a ContentObserver (code).
do you mean that it
I would start looking here:
http://code.google.com/android/reference/android/content/ContentResolver.html#registerContentObserver(android.net.Uri,
boolean, android.database.ContentObserver)
with ContentObserver.registerContentObserver which sounds like it
should do what you want. I haven't
I would start looking here:
http://code.google.com/android/reference/android/content/ContentResolver.html#registerContentObserver(android.net.Uri,
boolean, android.database.ContentObserver)
with ContentObserver.registerContentObserver which sounds like it
should do what you want. I haven't
Yes, this is the way to monitor for content provider changes. Note that
this is deliberately not done as a broadcast, you can only receive these
while you are running by explicitly registering for them, because we didn't
want to get in the situation of launching 1 or more apps every time some
5 matches
Mail list logo
