Repeating alarm in Calendar app

by Micropaint Calgary » Fri, 19 Mar 2010 05:41:56 GMT


Sponsored Links
 I come from a Palm background.  One of the wonderful things about the
Palm calendar was the ability to set repeating or recurring alarms for
an event that would continue until the user canceled the alarm.  I
don't see this in the Android calendar on my Milestone.

The alarm needs to repeat until the user cancels it
The default interval between alarms needs to be adjustable from a few
minutes to an hour or so.
The default number of repeats on the alarm needs to be adjustable by
the user.
The default alarm sound needs to be adjustable by the user.

The Android application "Remind Me" comes closest to what I need in
the Android world.  However, it is standalone, and its entries do not
appear in the Android calendar.  This means that I have to put my
reminders in two places -- in the Calendar so I don't 'double book',
and in Remind Me so that if I am unable to drop what I am doing to
tend to the reminder, it doesn't let me forget.

Presently, multiple alarms on a calendar event can be set, but it
appears that they have to be individually set, and they can only be
set prior to the event.  This is fine for 'must be there'
appointments.  It is cumbersome for 'must do sometime today'
reminders.  If I am driving and cannot tend to the reminder alarm on a
calendar event, I often forget that the alarm was triggered by the
time I get to my destination.  This is why I need the recurring
reminder.  My ability to forget knows no bounds.  :)

In scouring the web for information on this, I see that this is a
common request, but perhaps posted in places that the devs don't see.
I hope that posting this here will be helpful to further development
of the platform.

Thanks for listening.

Frank.

--



Other Threads

1. Learning from Mark Murphy's book - threading question



I wouldn't say that. There are plenty of scenarios in which you need to
manually create threads:

-- need finer-grained control over a thread pool than AsyncTask offers
-- waiting on server sockets
-- handling your own event loop in a game


There is no question that AsyncTask and IntentService are very useful
and, all else being equal, are probably the correct choice. However, I
would not say that forking your own threads is against "Android best
practices".

In the specific book example the OP was inquiring about, I show manual
thread management, just before showing AsyncTask.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy

_Android Programming Tutorials_ Version 1.1 Available!

--

2. How long does it take for an application to get indexed to the Marketplace?

I wrote two apps and submitted them to the marketplace last night
(been roughly 12 hours now).  One was a LITE version of my app and the
next was a Standard version. Neither shows up in a search on the
Marketplace even though the LITE version of my app has been installed
25 times already.  Is there a lengthy approval process that goes on
before an app is approved?

-- 

3. Learning from Mark Murphy's book - threading question

4. Location and security settings

5. Color animation

6. Application Idea, Need Assistance

7. What is the best way to store non-editable preferancies