diff -r 89d6a7a84779 -r 25a17d01db0c Symbian3/PDK/Source/GUID-CA933F35-7508-5C98-9DB6-2492803A2183.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/PDK/Source/GUID-CA933F35-7508-5C98-9DB6-2492803A2183.dita Fri Jan 22 18:26:19 2010 +0000 @@ -0,0 +1,29 @@ + + + + + +Reading a Skipped Alarm Property

The Publish and Subscribe framework enables a client to receive notification from the Alarm Server about the skipped alarm.

The value associated with the KMissingAlarmPubSubKey property is a TMissedAlarmPubSubData structure.

KMissingAlarmPubSubKey contains data about environmental changes and whether or not they have resulted in a skipped alarm.

The KMissingAlarmPubSubKey property value indicates if there are skipped alarms. The subscriber reads the current value of the property to determine if there are skipped alarms. A client more usually subscribes to the property and responds to any changes by calling the ReadSkippedAlarmPropertyL() function. iValue stores an integer that indicates if there are skipped alarms. #include <ASShdAlarm.h> // For TMissedAlarmPubSubData etc. +#include <…> +… +void CSkippedAlarmsObserver::ReadSkippedAlarmPropertyL() + { + TPckgBuf<TMissedAlarmPubSubData> skippedAlarmBuf; + + User::LeaveIfError(RProperty::Get(KAlarmServerPubSubCategory, KMissingAlarmPubSubKey, skippedAlarmBuf)); + + if (skippedAlarmBuf().iValue == 2) + { + HandleSkippedAlarmsL(); + } + } + This example illustrates the steps required to use the property value to establish if there are skipped alarms. Note: The example does not describe the procedure required to subscribe to the property. Working with Skipped + Calendar Alarms Reading a Skipped Alarm Instances + Property Retrieving Alarmed + Calendar Instances \ No newline at end of file