Top | ![]() |
![]() |
![]() |
![]() |
enum | ECalClientSourceType |
enum | ECalObjModType |
enum | ECalComponentVType |
enum | ECalComponentClassification |
enum | ECalComponentPeriodKind |
enum | ECalComponentRangeKind |
enum | ECalComponentTransparency |
enum | ECalComponentAlarmAction |
enum | ECalComponentAlarmTriggerKind |
enum | ECalRecurDescribeRecurrenceFlags |
enum | ECalOperationFlags |
Indicates the type of modification made to a calendar
Modify this component |
||
Modify this component and all prior occurrances |
||
Modify this component and all future occurrances |
||
Modify all occurrances of this component |
||
Modify only this component |
Since: 3.8
Types of calendar components to be stored by a ECalComponent, as per RFC 2445. We don't put the alarm component type here since we store alarms as separate structures inside the other "real" components.
Influences behaviour of e_cal_recur_describe_recurrence()
.
no extra flags, either returns |
||
either returns |
||
returns |
Since: 3.30
Calendar operation flags, to specify behavior in certain situations. The conflict
resolution mode flags cannot be combined together, where the E_CAL_OPERATION_FLAG_CONFLICT_KEEP_LOCAL
is the default behavior (and it is used when no other conflict resolution flag is set).
The flags can be ignored when the operation or the backend don't support it.
no operation flags defined |
||
conflict resolution mode, to fail and do not do any changes, when a conflict is detected |
||
conflict resolution mode, to use newer of the local and the server side data, when a conflict is detected |
||
conflict resolution mode, to use the server data (and local changed), when a conflict is detected |
||
conflict resolution mode, to use local data (and always overwrite server data), when a conflict is detected |
||
conflict resolution mode, to create a copy of the data, when a conflict is detected |
||
request to disable send of an iTip message by the server; this works only for servers which support iTip handling |
Since: 3.34