tsucheck wrote:Thank you both. Thats kind of what I expected, just wanted to make sure there is no other way of doing this.
chouputra, I had a followup question to your respose. Looking at the API example code that comes with the emulator there are few Alarm examples and in them all I see is an Activity that makes use of the Alarm Service and sets the timer. So really there is only the "alarm setting application" and the timer, no background application. So I'm not sure what you were refering to. Perhaps just my example wasn't explained well. But I would like to know what you meant in case I'm missing something. I'm assuming that the alarm is kind of Intent Receiver, even though it doesn't say that in the documentation so perhaps thats the background application that you meant.
On a different note, there was one additional architectural decision I was debating. I was thinking of having a service that actually does the alarm setting and the activity bind to that service. So initially it would spawn the service and any subsequent re-lunches would just connect to it (if the alarm was set). If user just exits the activity without setting the alarm no service would be started.
Users browsing this forum: Exabot [Bot], Google [Bot] and 15 guests