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 545261 - CAL_STATIC_CAPABILITY_CREATE_MESSAGES
CAL_STATIC_CAPABILITY_CREATE_MESSAGES
Status: RESOLVED NOTABUG
Product: evolution-data-server
Classification: Platform
Component: Calendar
2.24.x (obsolete)
Other All
: Normal major
: ---
Assigned To: Suman Manjunath
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-07-29 05:36 UTC by Suman Manjunath
Modified: 2013-09-14 16:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
Patch to add the new static capability. (2.42 KB, patch)
2008-07-29 05:37 UTC, Suman Manjunath
none Details | Review
Patch in Evolution to make use of the new capability. (1.41 KB, patch)
2008-07-29 05:50 UTC, Suman Manjunath
none Details | Review

Description Suman Manjunath 2008-07-29 05:36:15 UTC
+2008-07-18  Suman Manjunath  <msuman@novell.com>
+
+	** Added CAL_STATIC_CAPABILITY_CREATE_MESSAGES
+
+	* libecal/e-cal-util.h:
+	* libecal/e-cal.c (e_cal_get_create_messages): 
+	This static capability determines if a calendar backend can send
+	messages to recipients by itself. It is different from the 
+	CAL_STATIC_CAPABILITY_SAVE_SCHEDULES from the fact that this new
+	capability is processed after the user has been prompted to send an 
+	update. It is useful if the actual object needs some processing 
+	after the messages are sent. 
+
Comment 1 Suman Manjunath 2008-07-29 05:37:10 UTC
Created attachment 115474 [details] [review]
Patch to add the new static capability.
Comment 2 Suman Manjunath 2008-07-29 05:50:06 UTC
Created attachment 115475 [details] [review]
Patch in Evolution to make use of the new capability.
Comment 3 Suman Manjunath 2008-07-29 06:10:51 UTC
From bug #545263, the attached patches are obsolete. 
Comment 4 Chenthill P 2008-08-06 08:09:37 UTC
This is not a bug...