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.
On Fri, Aug 7, 2009 at 12:16 PM, SR <[email protected]> wrote: > > Ultimately, the only way I could get different intents to be scheduled > with AlarmManager is to set different data URIs in the Intents that I > was wrapping in PendingIntents and scheduling with AlarmManager.set(). > > I filed an issue about this here: > http://code.google.com/p/android/issues/detail?id=3498 > > Stan > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
