Symbian3/PDK/Source/GUID-49363088-CE0B-558D-8E86-48400E4F7C2F.dita
changeset 12 80ef3a206772
parent 9 59758314f811
child 14 578be2adaf3e
equal deleted inserted replaced
11:5072524fcc79 12:80ef3a206772
    44 same time. </p> <p>To support multiple alarm notification, Alarm Server notifies
    44 same time. </p> <p>To support multiple alarm notification, Alarm Server notifies
    45 Alert Server about multiple expired alarms without waiting for the first alarm
    45 Alert Server about multiple expired alarms without waiting for the first alarm
    46 to be cleared or snoozed. </p> <fig id="GUID-4F324FD2-EB30-5910-BD8E-315B67A4FA44">
    46 to be cleared or snoozed. </p> <fig id="GUID-4F324FD2-EB30-5910-BD8E-315B67A4FA44">
    47 <title>              Alarm state diagram for multiple alarm notification 
    47 <title>              Alarm state diagram for multiple alarm notification 
    48             support            </title>
    48             support            </title>
    49 <image href="GUID-16B42854-F27D-5CB3-BCFE-8F711793EE60_d0e603974_href.png" placement="inline"/>
    49 <image href="GUID-16B42854-F27D-5CB3-BCFE-8F711793EE60_d0e582704_href.png" placement="inline"/>
    50 </fig> <p>In the diagram above, a queued alarm can change to the ‘waiting
    50 </fig> <p>In the diagram above, a queued alarm can change to the ‘waiting
    51 to notify’ state if an alarm has expired but the maximum number of notifying
    51 to notify’ state if an alarm has expired but the maximum number of notifying
    52 alarms has been reached. The state can also change if Alarm Server is waiting
    52 alarms has been reached. The state can also change if Alarm Server is waiting
    53 for a reply from Alert Server. This second scenario may occur because even
    53 for a reply from Alert Server. This second scenario may occur because even
    54 though Alert Server can accept multiple alarms, the Alarm Server needs the
    54 though Alert Server can accept multiple alarms, the Alarm Server needs the