| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
1999-01-28 Miguel de Icaza <miguel@nuclecu.unam.mx>
* calendar.c (calendar_init_alarms): Schedule an alarm for
midnight to change the calendar_day_begin/calendar_day_end.
* alarm.c (alarm_ready): If we reschedule, there is no need to
activate any pending alarms.
svn path=/trunk/; revision=634
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1998-12-16 Miguel de Icaza <miguel@nuclecu.unam.mx>
Rewrote the old and broken alarm system. It never actually
worked properly. Now it works properly, and I figured a nice way
to get the Audio alarm do something nicer (it is now like an alarm
clock :-).
* gnome-cal.c (calendar_notify): Now we take a CalendarAlarm to
actually distinguish which alarm was triggered.
* alarm.c (alarm_ready): The code was only activating the first
alarm. Reschedule the timer upon delivery of an alarm.
svn path=/trunk/; revision=535
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
1998-08-03 Federico Mena Quintero <federico@nuclecu.unam.mx>
* main.c (about_calendar_cmd): Use an array of const strings to
keep gcc happy.
* alarm.c (alarm_compare_by_time): Use gconstpointer to keep gcc happy.
* calendar.c (calendar_object_compare_by_start): Likewise.
* gncal-full-day.c (child_compare_by_start): Likewise.
svn path=/trunk/; revision=296
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Lots of fixes:
1. Alarms are rescheduled when an event has been changed.
2. Avoid emitting spurious event changes.
3. Applied black magic to get the mail-notification
working.
Miguel.
svn path=/trunk/; revision=199
|
| |
|
|
| |
svn path=/trunk/; revision=161
|
|
|
Yes.
It works.
It loads, it saves, it does all that stuff.
It works, even if federico complains that we did not test close.
Repetition, alarms, all that stuff you all guys love.
It it is there. We did minimal testing, but we know you will
happilly commit a fix if you find a problem, right?
Ok, we are off to a party now.
Miguel
svn path=/trunk/; revision=155
|
