GNOME Bugzilla – Bug 248109
Cannot change the options of a reminder
Last modified: 2009-06-30 16:11:39 UTC
Description of Problem: In the Reminder tab of the New Appointment window, create three alarms in the following order: message, sound, and program. Select the message alarm, and click on the Options button. The details of the program alarm are displayed instead of the details of the message alarm. Steps to reproduce the problem: 1. Invoke Calendar. 2. Create an appointment. 3. In the Reminder tab, create three reminders. 4. Try to edit a reminder after you have added the reminder to the Action/Trigger list. Actual Results: Displays details of last reminder created. Expected Results: Should display details of currently selected reminder. Should be able to change these details. How often does this happen? Every time. Additional Information: Evolution 1.4.
reproducable using evolution-1.4.6.0.200403120630-0.snap.ximian.8.1. very related to bug 225816 (in both cases the "options"-button does not work properly)! since some ui-changes for 1.5.7/2.0 have taken place (take a look at http://primates.ximian.com/~anna/editors/meet-reminders.png), i wonder if these options will still be available and if this is still an issue...
still wrong in evolution1.5-1.5.9.0.200406211628-0.snap.ximian.8.1. this is a very annoying restriction which makes it totally useless to use more than one alarm of a different type. (caution: naive point of view:) isn't this just about checking which alarm is highlighted in the list and then opening the right options dialog? you can undo but i'll target this to 2.1 (and i've closed two bugs today that were targetted to 2.1, so don't contradict me ;-).
*** bug 241819 has been marked as a duplicate of this bug. ***
there is no possibility to change options of a reminder at all since 2.0's design changes - so this one depends on bug 234552.
futuring.
UI changed before and after bug #225816, which was fixed in 2006, thus I'm marking this one as a duplicate. Btw, it works as expected on today's master. *** This bug has been marked as a duplicate of 225816 ***