aboutsummaryrefslogtreecommitdiffstats
path: root/calendar/alarm.c
Commit message (Collapse)AuthorAgeFilesLines
* More file moving action - FedericoFederico Mena Quintero2000-03-061-250/+0
| | | | svn path=/trunk/; revision=2061
* this is not right, but it gets this closer to building.Seth Alves2000-03-041-1/+1
| | | | svn path=/trunk/; revision=2035
* Debugging enhancements: report alarms not added (because they have alreadyRussell Steinthal1999-12-031-10/+42
| | | | | | passed), allow toggling of debugging output using SIGUSR1 svn path=/trunk/; revision=1453
* Style fix.Russell Steinthal1999-10-221-1/+2
| | | | svn path=/trunk/; revision=1341
* Commit debugging support to HEAD as well; there's no good reason to have ↵Russell Steinthal1999-10-221-1/+37
| | | | | | debugging in the stable but not devel version, is there? svn path=/trunk/; revision=1340
* Release points here.Miguel de Icaza1999-08-061-1/+1
| | | | | | | | 1999-07-30 Miguel de Icaza <miguel@gnu.org> * month-view.c (month_view_init): Release points here. svn path=/trunk/; revision=1085
* Schedule an alarm for midnight to change theMiguel de Icaza1999-01-291-2/+12
| | | | | | | | | | | | 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
* Rewrote the old and broken alarm system. It never actually workedMiguel de Icaza1998-12-171-7/+33
| | | | | | | | | | | | | | | | | 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
* Use an array of const strings to keep gcc happy.Federico Mena Quintero1998-08-041-3/+3
| | | | | | | | | | | | | 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:Arturo Espinosa1998-04-291-2/+3
| | | | | | | | | | | | | 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
* More touches -migArturo Espinosa1998-04-191-1/+0
| | | | svn path=/trunk/; revision=161
* Yes.Arturo Espinosa1998-04-181-0/+145
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