Re: [Evolution] Hundreds of alarms

On Thu, 2004-01-08 at 10:50 -0700, Brett Johnson wrote:
On Wed, 2004-01-07 at 16:30, Rodrigo Moya wrote:
I am only one of the developers, and of course, I don't have the final

Yeah, I'm just acknowledging that I'm not a Ximian developer, so you
don't have to accept my feedback any more than you'd have to accept a
patch from me (although obviously, I hope you would accept either ;o)

so far, I have accepted your feedback, so if you want, try sending a
patch and I'll prove you I accept both :-)

in addition, I also sync my calendar with a palm PDA.  99.99% of the
time, I first get notified of an event by my PDA.  It's incredibly
annoying to be notified 3 more times, after the event has passed, the
next time I start up evolution on one of my other machines.

right, I understand the problem. But this can be solved in better ways
than having the config option you mention. We could make the file
backend remove the alarms that have been notified already, thus
preventing the alarms to pop up once on every machine.

1) How could the file backend possibly know that my PDA has already
notified me?

right. The PDA does what evolution does, which is to store somewhere
which alarms have been notified and which not. This is internal to the
apps, so the only way to make this work would be to make all apps remove
the alarm when notified, so that it never pops up again. This seems
wrong to me, since you might want to keep the original ical component,
to move it to another date or whatever.

2) Given #1, this wouldn't change anything for my usage pattern.  I.e.
if I get notified (redundantly) on my laptop, then I sync my laptop's
~/evolution directory to the other machines, I already won't get
notified multiple times.  If I don't sync, the backend can't possibly
know that I've been notified on another machine, so I'll get redundantly
notified again.

right, but this will happen with any app you use to view the data, since
none of them actually remove the alarm. Probably it would be a nice idea
to have RFC2445 allow a property on alarms to specify they have been
already notified. That would work perfectly well for all apps.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]