|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-579EF7F5-EA93-40D1-917F-95B966D1BAB2" xml:lang="en"><title>Working |
|
13 with Skipped Calendar Alarms - Overview</title><shortdesc>This topic introduces a set of tutorials on working with Calendar |
|
14 alarms that have been skipped because of environment changes. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
15 <section id="GUID-D75C3FEA-664E-4526-872E-BFC73BAF6F64"> <title>Required background</title> <p>Familiarity with:</p><ul> |
|
16 <li><p><xref href="GUID-00631ED2-1B7F-5FC4-9E81-4B6DF7946631.dita">Calendar</xref> and <xref href="GUID-114D4F3F-9358-5B50-94DC-45CCBA783DF4.dita">Alarm Server</xref> functionality.</p></li> |
|
17 <li><p>Skipped Alarms property keys in the <xref href="GUID-8FAC10FB-BCD1-3373-9440-EF2EED70A861.dita"><apiname>TASShdAlarm</apiname></xref> class.</p></li> |
|
18 <li><p><xref href="GUID-C705B0D5-055A-5DAA-9C6E-2FC3519FA50C.dita">Publish and |
|
19 Subscribe</xref>. </p></li> |
|
20 </ul> </section> |
|
21 <section id="GUID-7A034BBB-52F3-4AFA-B40E-26B563491255"> <title>Introduction</title> <p> A skipped alarm is a |
|
22 Calendar alarm which does not expire normally because of an environment change. |
|
23 An environment change can put the alarm’s expiry time in the past. </p><p> An |
|
24 environment change is one of the following: </p><ul> |
|
25 <li><p>A system time change. </p></li> |
|
26 <li><p>A time zone change. This is similar to a Coordinated Universal Time |
|
27 (UTC) change. </p></li> |
|
28 <li><p>A Daylight Savings Time (DST) observation period beginning or ending. |
|
29 (Similar to a UTC change.) </p></li> |
|
30 </ul><p> Each Calendar instance has a <xref href="GUID-725D11A2-8805-3466-98DB-EF5CDEAF2801.dita"><apiname>CCalEntry</apiname></xref>. When the <codeph>CCalEntry</codeph> has |
|
31 an associated <xref href="GUID-211D3640-9862-3F78-98FC-9793578117A9.dita"><apiname>CCalAlarm</apiname></xref> it becomes an alarmed Calendar |
|
32 instance. </p><p> When an environment change occurs the Alarm Server can respond |
|
33 to the skipped alarms in one of two ways: </p><p> <i>Queue an alarm which |
|
34 then expires</i></p><p>The Alarm Server notifies Calendar that the system |
|
35 date/time has changed. Calendar then queues alarms that would have been skipped |
|
36 up to a day in the past with the Alarm Server. These alarms then expire immediately |
|
37 and the device user must acknowledge each of them. </p><p><i>Notify a subscriber |
|
38 about the skipped alarm</i></p><p> The Alarm Server uses Publish and Subscribe |
|
39 to notify a subscriber that one or more Calendar alarms has been skipped. |
|
40 The subscriber decides what action to take because Calendar does not queue |
|
41 skipped alarms with the Alarm Server. </p><p>To learn how a subscriber can |
|
42 be notified of skipped Calendar alarms and respond to them see the tasks below.</p> |
|
43 </section> |
|
44 <section id="GUID-95A0061F-EFAC-44FB-93C1-7D6BDB6C8A25"> <title>Tasks</title><ul> |
|
45 <li><p><xref href="GUID-CA933F35-7508-5C98-9DB6-2492803A2183.dita">Reading a Skipped |
|
46 Alarm Property</xref></p></li> |
|
47 <li><p><xref href="GUID-BF8C56B7-1F39-502F-B9CA-81E9272CC945.dita">Reading a Skipped |
|
48 Alarm Instances Property</xref></p></li> |
|
49 <li><p><xref href="GUID-E3981A14-DD2C-5582-A250-C2AD358729FD.dita">Retrieving Skipped |
|
50 Alarmed Calendar Instances</xref></p></li> |
|
51 </ul> </section> |
|
52 </conbody></concept> |