On Fri, Aug 7, 2009 at 12:53 PM, SR <[email protected]> wrote: > Ok, then the documentation should not imply that AlarmManager.set(...) > uses filterEquals(...) to compare the intents. It should say instead > that (action, type, Uri, categories, component) are used for > comparison of intents.
It does use filterEquals(). > Also, the documentation for PendingIntent currently explicitly says > that the request code is ignored. If it is not ignored by > AlarmManager, the documentation must say that too. It depends on what you mean by ignored. It is ignored as far as delivering the pending intent goes, because broadcasts don't (currently) have requests codes. It is not ignored for intent matching, but taken as another identifying part of the pending intent. And none of this has anything specifically to do with the alarm manager, which just gets pending intents, and calls equals() and send() on them. Anyway, I do agree the documentation needs to be improved; the identity of pending intents is one of the more common issues I see people having. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
