gui/comp-editor-factory.c (edit_existing),

* gui/calendar-component.c (create_new_event):
* gui/e-calendar-view.c: (e_calendar_view_edit_appointment):
* gui/comp-editor-factory.c (edit_existing),
* (edit_new):
* gui/dialogs/event-editor.c
* (event_editor_edit_comp),
 (event_editor_new): updated the calls to event_editor_new
with additional argument.
* gui/dialogs/event-editor.h:
* add parameter
* is_meeting to
distinguish between events and  meetings.
* gui/dialogs/meeting-page.c:
* (sensitize_widgets):
use explicit GError variable so that BUSY_ERROR
conditions do not lead us to think the calendar is readonly.
* gui/e-meeting-store.c:
* (refresh_queue_remove),
* (ems_init),
(e_meeting_store_remove_attendee), (freebusy_async),
(refresh_busy_periods), (refresh_queue_add): Make free-busy calls
to backends async. Fixed the problem of spurious attendees getting
added to the refresh_data.

svn path=/trunk/; revision=27614

1 files changed, 8 insertions, 5 deletions

diff --git a/calendar/gui/dialogs/meeting-page.c b/calendar/gui/dialogs/meeting-page.c
index 241712a006..19faebaec4 100644
--- a/calendar/gui/dialogs/meeting-page.c
+++ b/calendar/gui/dialogs/meeting-page.c
@@ -305,12 +305,15 @@ clear_widgets (MeetingPage *mpage)
 static void
 sensitize_widgets (MeetingPage *mpage)
 {
-	gboolean read_only;
+	gboolean read_only = FALSE, user_org;
 	MeetingPagePrivate *priv = mpage->priv;
-
-	if (!e_cal_is_read_only (COMP_EDITOR_PAGE (mpage)->client, &read_only, NULL))
-		read_only = TRUE;
-
+	GError *error = NULL;
+	
+	if (!e_cal_is_read_only (COMP_EDITOR_PAGE (mpage)->client, &read_only, &error)) {
+		if (error->code != E_CALENDAR_STATUS_BUSY)
+			read_only = TRUE;
+		g_error_free (error);
+	}	
 	gtk_widget_set_sensitive (priv->organizer, !read_only);
 	gtk_widget_set_sensitive (priv->existing_organizer_btn, !read_only);
 	gtk_widget_set_sensitive (priv->add, !read_only && priv->user_org);