CBattery Non-MFC Class

Environment: Visual C++ 6 SP3

CBattery is a non-MFC class wrapper for the battery related Windows Power Management API functions. It may be used by notebook/laptops system utilities developed with Visual C++.



CBattery implements the following public methods:
 - BOOL SystemPowerStatusLoaded()
 - BOOL ReloadSystemPowerStatus()
 - SYSTEM_POWER_STATUS SystemPowerStatus()
 - CBattery::AC_LINE_STATUS ACLineStatus()
 - CBattery::BATTERY_FLAG BatteryFlag()
 - CBattery::BOOL BatteryCharging()
 - BYTE BatteryLifePercent()
 - long BatteryFullTime()
 - long BatteryLifeTime()
 - BOOL BatteryIsUnknown()
 - BOOL BatteryIsCharging()
 - CBattery::DEVICE_POWER_STATE GetDevicePowerState()
 - void SetDevice(HANDLE hDevice)
 - HANDLE GetDevice()

CBattery contains the following public constants:
 - Line status:
   ACLS_OFFLINE
   ACLS_ONLINE
   ACLS_UNKNOWN

 - Battery status flags:
   BF_HIGH
   BF_LOW
   BF_CRITICAL
   BF_CHARGING
   BF_NO_BATTERY
   BF_UNKNOWN
 
- Device power state:
   DPS_OFF
   DPS_ON
   DPS_UNKNOWN

 - General constants:
   UNKNOWN_BATTERY_LIFE_PERCENT
   UNKNOWN_BATTERY_FULL_TIME
   UNKNOWN_BATTERY_LIFE_TIME
   UNKNOWN_DEVICE_POWER_STATE


Notes:
 
- The system is only capable of estimating BatteryFullTime based on calculations on BatteryLifeTime and BatteryLifePercent. Without smart battery subsystems, this value may not be accurate enough to be useful.
 - The class does not use the Sysinfo OCX control.
 - The system broadcasts the PBT_APMPOWERSTATUSCHANGE event to all applications when the power status changes. When your application receives this event, it should call the methods of the class again to determine what changed.
 - Power management specifications and white papers from the OnNow initiative home page are located at www.microsoft.com/hwdev/onnow.htm.
 - The PBT_* messages are documented in the SDKs PBT.H.
 - An application can use CBattery::GetDevicePowerState to determine whether a disk or other device is spun up. If the device is not spun up, the application should defer accessing it.
 - For more details about APM, one should check the Platform SDK: Hardware.
 - Unfortunately, power management features dont work in Windows NT 4.0! However, if youre using a specialized version of Windows NT, modified by your computer manufacturer, the methods may work.
 - The demo included application does not use all the all methods implemented in the CBattery class. Check the Battery.cpp and Battery.h files for the class source code.

Downloads

Download source - 2 Kb
Download demo application - 40 Kb


Comments

  • for display

    Posted by Legacy on 01/11/2002 12:00am

    Originally posted by: skon

    how use GetDevicePowerState for display??
    
    for i know monitor is off or on?

    HDC monitor;
    monitor = GetDC( NULL );
    if ( GetDevicePowerState (monitor) )
    .....

    not work.... :(

    Reply
  • Getting battery information in detail

    Posted by Legacy on 06/05/2001 12:00am

    Originally posted by: Shravan kumar

    Hi,
    I am writing a test program for to test the energy or charge levels of my(ACPI)Battery , related
    information like Finding full charged capacity etc.... on windows platform. In this i am sending a IOCTL_BATTERY_SET_INFORMATION with a call to DeviceIoControl( ) function. The first parameter of this function is hDevice [in] Handle to the device which can be obtained by CreateFile( ) functiion. Till now it is ok but what shall i pass as the first parameter ti this CreateFile( ) function which is a Pointer to a null-terminated string that specifies the name of the object to create or open.
    If any one can help me regarding this it will be a great
    help for me. Or where can i get the related source code regarding this.??

    Please mail your suggestions to:
    S.Gande@zensar.com

    Thanks & Regards
    Shravan


    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Today's agile organizations pose operations teams with a tremendous challenge: to deploy new releases to production immediately after development and testing is completed. To ensure that applications are deployed successfully, an automatic and transparent process is required. We refer to this process as Zero Touch Deployment™. This white paper reviews two approaches to Zero Touch Deployment--a script-based solution and a release automation platform. The article discusses how each can solve the key …

  • On-demand Event Event Date: October 29, 2014 It's well understood how critical version control is for code. However, its importance to DevOps isn't always recognized. The 2014 DevOps Survey of Practice shows that one of the key predictors of DevOps success is putting all production environment artifacts into version control. In this webcast, Gene Kim discusses these survey findings and shares woeful tales of artifact management gone wrong! Gene also shares examples of how high-performing DevOps …

Most Popular Programming Stories

More for Developers

RSS Feeds