After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 380644 - "Required Participants" dialog does not show meeting participants
"Required Participants" dialog does not show meeting participants
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Milan Crha
Evolution QA team
: 436615 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-29 20:40 UTC by Matthew Barnes
Modified: 2013-09-13 00:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proposed patch (3.28 KB, patch)
2006-12-12 02:29 UTC, Matthew Barnes
accepted-commit_now Details | Review
proposed evo patch (7.27 KB, patch)
2007-10-26 09:36 UTC, Milan Crha
committed Details | Review

Description Matthew Barnes 2006-11-29 20:40:54 UTC
Forwarding this from a downstream bug report:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=215467

Confirmed that this still exists in Evolution 2.9.2.

Steps to Reproduce:
1. Launch Evolution's Calendar component.
2. Create a new meeting and add a few participants.
3. Save the meeting, then re-open it from the calendar.
4. Click the "Attendees" button to bring up the "Required Participants" dialog.

Actual Results:
There are no participants listed in the "Required Participants" dialog.  Closing this dialog then updates the participant list in the "Meeting" dialog, which effectively blows away all the participants.

Expected Results:
The participants listed in the "Meeting" dialog should be listed in the appropriate section(s) of the "Required Participants" dialog.
Comment 1 Matthew Barnes 2006-12-12 02:29:57 UTC
Created attachment 78179 [details] [review]
Proposed patch

This patch keeps the "Required Participants" dialog up-to-date by connecting the EMeetingListView to the EMeetingStore's "row-inserted" and "row-deleted" signals and then forwarding those events to the ENameSelector.

It has one known side-effect.  The following warning is generated for each participant when opening a meeting from the calendar:

    e-data-server-ui-WARNING **: Same destination added more than once to
    EDestinationStore!

I've not yet traced the root cause of this warning, but it seems harmless.
Comment 2 Harish Krishnaswamy 2007-03-05 17:31:01 UTC
On opening the editor, e_meeting_store_add_attendee updates the store with the current set of attendees. The callback you have added in your patch updates the store again (e_destination_store_append_destination) - which is the source of the warning. The patch looks fine otherwise. 
Comment 3 Matthew Barnes 2007-03-05 17:54:29 UTC
Harish, thanks for the tip.  I'll get the warning fixed before committing.
Comment 4 Kjartan Maraas 2007-04-17 21:28:17 UTC
So, are you going to commit this?
Comment 5 Matthew Barnes 2007-04-18 00:57:21 UTC
Yes.  I still want to try to get the warning fixed first.
Comment 6 Srinivasa Ragavan 2007-06-18 04:51:21 UTC
Matthew, can you look at this? 
Comment 7 Milan Crha 2007-10-26 09:36:48 UTC
Created attachment 97897 [details] [review]
proposed evo patch

for evolution;

There was similar issue in task-editor too, so I changed it on both places. Because everything else work like expected, so I drop Matt's solution with attached signals, instead of that I added new functions to add attendees to name selector and name store in one place, so we keep consistent.

Remove attendee in task-editor was broken too, so fixed now.

From original patch I kept two Matt's changes, I named it code cleanup, even I'm not sure why he did there those changes.
Comment 8 Srinivasa Ragavan 2007-11-26 02:53:07 UTC
Milan, I tested your patch also. it works fine and no warnings or anything. Commit to stable/head (Since no string changes)
Comment 9 Milan Crha 2007-11-26 10:19:51 UTC
Committed to trunk. Committed revision 34582.
Committed to stable. Committed revision 34583.
Comment 10 Paul Smith 2007-12-04 07:17:42 UTC
*** Bug 436615 has been marked as a duplicate of this bug. ***