See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Power Manager makes system power state transitions under the following circumstances:
- An OEM-specific event that requires a state change.
- An application calls the
SetSystemPowerStatefunction.
OEM-specific events might include going from AC power to battery power, prolonged periods of system inactivity, insertion into a cradle, low battery levels, and so on. The OEM is responsible for customizing Power Manager to recognize when transitions between system power states are appropriate and for carrying them out when necessary. The base power management sources included with Platform Builder recognize AC-to-battery power transitions.
Applications can call SetSystemPowerStatewith an explicit power state name or a predefined system power state constant. Applications that have the OEM-specific system power states can use explicit power state names. Platform-independent applications generally set POWER_STATE_XXX flags instead, and allow Power Manager to determine which OEM-specific power state fits best. Power Manager can restrict the states that applications can request.