Dianne,
Thanks! I think I figured it out about 30 minutes ago. In the
AlarmManager.set(..) documentation, it says that intents are compared
using Intent.filterEquals(Intent otherIntent), which, of course, does
not compare the extras.
One quick (and dirty) workaround would be to extend Intent with your
own class that goes something like this:
public class AlarmManagerIntent extends android.content.Intent {
// Add other requisite constructors here
AlarmManagerIntent(Context ctx, Class<?> c) {
super(ctx, c);
}
@Override
public boolean filterEquals(Intent i) {
return (i == this);
}
}
Use it only when certain that your scheduled Intents will be unique!
Let me test this and see if it works...
Stan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
