Mike Temporale
08-12-2005, 06:45 PM
<div class='os_post_top_link'><a href='http://blogs.msdn.com/windowsmobile/archive/2005/08/11/450591.aspx' target='_blank'>http://blogs.msdn.com/windowsmobile/archive/2005/08/11/450591.aspx</a><br /><br /></div><i>"The previous techniques were to not burn CPU cycles (i.e. animate something) if your app wasn't in the foreground, and to only animate for so long after your app received input. But what if your code is hosted in some other app and you don't really know if you're in the foreground? And what if you don't really ever receive input? Wouldn't it be nice if there was some component in the system that kept track of all of this? And wouldn't it be even better if that component could tell us when it's time for us to clamp down and stop burning cycles? In fact, that component does exist, and it can tell you what's going on in the system. The component is Power Manager and it has a mechanism for signaling you whenever a System Power State transition happens."</i><br /><br />Mike Calligaro continues his blog postings about power consumption in the Windows Mobile world. While this article is focused on developers, I think a lot of good information in it for all of us. It might help you think twice about installing some hacked up homescreen plugin. ;)