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.
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. Stan On Aug 7, 3:27 pm, Dianne Hackborn <hack...@android.com> wrote: > Thanks. I closed the bug with a description of why this is so. Having data > (action, type, Uri, categories, component) that is unique within the intent > is the way to do this. You can also use the request code to disambiguate > them. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
