I do something similar to Brian but, since I have just a few Intents to manage, I store strings in the Shared Preferences database. It's simpler to use than SQLite if you just have a few pieces of (serializable) data.
On Aug 29, 6:03 am, Brian Swartzfager <[email protected]> wrote: > I just recently released an app where notification messages are > generated from records in a SQLite table. To create a unique action/ > id for my alarm intents, I take the primary key of the database record > and combine it with the package name for my app: > > ... > String intentId= "org.myDomainName.MyAppName_" + > recordPrimaryKeyValue; > Intent AlarmIntent= new Intent(SetAlarm.this, MsgNotification.class); > AlarmIntent.setAction(intentId); > ... > > That way, if the user does something to the record that requires > canceling the Pending Intent for the alarm, I can regenerate the same > intentId based off of the record, and using the package name ensures > that I'm only canceling an intent generated by my app and not another > app. > > --Brian -- 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
