Walles wrote: > I'll use a Service instead of an Alarm and keep it running in the > background. That way I can keep track of it myself.
Please don't. For starters, it won't work, since the service may get killed off by the user or the system. Also, while the service is in memory, you are taking up one process' worth of RAM. If you could explain to us what the effect is you are trying to achieve (versus low-level technical statements, like "not to overwrite an existing alarm with a new one"), we might be able to suggest alternative patterns. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 1.0 In Print! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
