nn::os::Alarm Class

class Alarm : 
    private nn::os::QueueableWaitTask,
    private ADLFireWall::NonCopyable

Class for handling alarms.

Alarms use the timer functionality of the OS to call a handler after the specified time has elapsed. When the handler is called, its first argument is the argument that was used when the alarm was set, and its second argument is false.

(The content of this paragraph is subject to change.) You must call InitializeAlarmSystem before using this class. Alarm handlers are run in certain specific threads, and in the current implementation, the number of these threads is limited to four. As a result, the alarm system will become unstable if you register many handlers that take a long time to complete (for example, those that perform thread blocking). (Content is subject to change up to here.)

There are two types of alarms: one-shot alarms and periodic alarms.

One-shot alarms are set using SetOneShot and cause a handler to be called after a fixed period of time. After calling either of these functions once, it is not possible to call SetOneShot or SetPeriodic again until the handler starts. These setter functions can be called again within the handler.

Periodic alarms are set using SetPeriodic and cause a handler to be called periodically thereafter. It is not possible to call either SetOneShot or SetPeriodic again while a periodic alarm is active.

You can cancel an alarm before the handler has run by calling Cancel. If the handler has already started, the handler will not be cancelled even if you call Cancel. If Cancel is called while an alarm is set (before a periodic alarm or one-shot alarm calls the handler), the alarm handler is called with its second argument set to true.

ADLFireWall::NonCopyable
  nn::fnd::IntrusiveQueue
    nn::os::QueueableTask
      nn::os::QueueableWaitTask
        nn::os::Alarm

2010/01/07

Initial version.