While extending calendar I noticed that the alarm widgets will be set
with the wrong data from other widgets. This is based on the fact that
the last alarm is past to these functions, i.e alarm_to_aalarm_widget,
alarm_to_dalarm_widget, alarm_to_malarm_widget, alarm_to_palarm_widget.
For example, filling out a message for the Display dialog will set the
args for a program to run to this message if an alarm to run a program
is added for the same appointment.
Since these set widget function don't do much good. I have taken the
code out of compile,i.e #if 0 ....#endif;
evolution-1.1.90-rc1
file: evolution-1.1.90/calendar/gui/dialogs/alarm-options.c
Ronald
--- evolution-1.1.90/calendar/gui/dialogs/alarm-options.c Mon Oct 7 15:22:27
2002
+++ evolution-1.1.90-new/calendar/gui/dialogs/alarm-options.c Wed Nov 6 22:54:11
+2002
@@ -205,6 +205,7 @@
static void
alarm_to_aalarm_widgets (Dialog *dialog, CalComponentAlarm *alarm)
{
+#if 0
icalattach *attach;
const char *url;
@@ -227,17 +228,20 @@
e_dialog_editable_set (dialog->aalarm_attach, url);
icalattach_unref (attach);
+#endif
}
/* Fills the display alarm widgets with the values from the alarm component */
static void
alarm_to_dalarm_widgets (Dialog *dialog, CalComponentAlarm *alarm)
{
+#if 0
CalComponentText description;
cal_component_alarm_get_description (alarm, &description);
e_dialog_editable_set (dialog->dalarm_description, description.value);
+#endif
}
/* Fills the mail alarm widgets with the values from the alarm component */
@@ -251,6 +255,7 @@
static void
alarm_to_palarm_widgets (Dialog *dialog, CalComponentAlarm *alarm)
{
+#if 0
icalattach *attach;
CalComponentText description;
@@ -271,6 +276,7 @@
}
e_dialog_editable_set (dialog->palarm_args, description.value);
+#endif
}
enum duration_units {
