<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: gnome-power-manager and multiple batteries</title>
	<atom:link href="http://blogs.gnome.org/hughsie/2009/06/16/gnome-power-manager-and-multiple-batteries/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/hughsie/2009/06/16/gnome-power-manager-and-multiple-batteries/</link>
	<description>Blog about geeky stuff</description>
	<lastBuildDate>Sun, 22 Nov 2009 00:10:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: hughsie</title>
		<link>http://blogs.gnome.org/hughsie/2009/06/16/gnome-power-manager-and-multiple-batteries/comment-page-1/#comment-1245</link>
		<dc:creator>hughsie</dc:creator>
		<pubDate>Wed, 17 Jun 2009 07:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=355#comment-1245</guid>
		<description>&gt;it was essentially throwing away information about the reported charge levels of each individual battery

I know, it sucked. The new way of doing things should be The Right Way (tm).</description>
		<content:encoded><![CDATA[<p>>it was essentially throwing away information about the reported charge levels of each individual battery</p>
<p>I know, it sucked. The new way of doing things should be The Right Way &#8482;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hughsie</title>
		<link>http://blogs.gnome.org/hughsie/2009/06/16/gnome-power-manager-and-multiple-batteries/comment-page-1/#comment-1244</link>
		<dc:creator>hughsie</dc:creator>
		<pubDate>Wed, 17 Jun 2009 07:06:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=355#comment-1244</guid>
		<description>&gt;that only considers the presence of a laptop battery, not any other kind of battery

We only show the mouse battery icon if it&#039;s low -- we try not to show the icon unless it&#039;s going to be useful.</description>
		<content:encoded><![CDATA[<p>>that only considers the presence of a laptop battery, not any other kind of battery</p>
<p>We only show the mouse battery icon if it&#8217;s low &#8212; we try not to show the icon unless it&#8217;s going to be useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Henstridge</title>
		<link>http://blogs.gnome.org/hughsie/2009/06/16/gnome-power-manager-and-multiple-batteries/comment-page-1/#comment-1242</link>
		<dc:creator>James Henstridge</dc:creator>
		<pubDate>Wed, 17 Jun 2009 01:55:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=355#comment-1242</guid>
		<description>This is great news.  I&#039;ll have to give it a try some time.

I had a look at the code in the 2.24 codebase a while back and thought it looked a bit weird.  By tracking a discharge profile of the combined virtual battery, it was essentially throwing away information about the reported charge levels of each individual battery.  With one of the batteries in my laptop failing at the time, the erratic readings from that battery basically ruined the accuracy of the readings on the other one.

Also, the design looked like it prevented carrying over discharge profiles for a battery when used together with a second battery and when used alone.

It&#039;s good to hear that things are improving.</description>
		<content:encoded><![CDATA[<p>This is great news.  I&#8217;ll have to give it a try some time.</p>
<p>I had a look at the code in the 2.24 codebase a while back and thought it looked a bit weird.  By tracking a discharge profile of the combined virtual battery, it was essentially throwing away information about the reported charge levels of each individual battery.  With one of the batteries in my laptop failing at the time, the erratic readings from that battery basically ruined the accuracy of the readings on the other one.</p>
<p>Also, the design looked like it prevented carrying over discharge profiles for a battery when used together with a second battery and when used alone.</p>
<p>It&#8217;s good to hear that things are improving.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Williamson</title>
		<link>http://blogs.gnome.org/hughsie/2009/06/16/gnome-power-manager-and-multiple-batteries/comment-page-1/#comment-1241</link>
		<dc:creator>Adam Williamson</dc:creator>
		<pubDate>Tue, 16 Jun 2009 17:44:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=355#comment-1241</guid>
		<description>This prompted me to poke a bit of g-p-m I hadn&#039;t looked at for a bit: wireless mouse handling.

I thought this was broken, but it&#039;s actually not - if I plug in a wireless mouse and set the icon policy to &#039;always&#039;, I get an icon in the notification area which tells me the charge level of the mouse. Shiny. But the icon doesn&#039;t show up if the icon policy is set to &#039;present&#039; - I guess that only considers the presence of a laptop battery, not any other kind of battery...

Also, gnome-power-preferences only lets you set the &#039;always&#039; or &#039;never&#039; policies for the icon. That seems somewhat over-simplified. I can&#039;t see why the UI shouldn&#039;t expose the other choices too.</description>
		<content:encoded><![CDATA[<p>This prompted me to poke a bit of g-p-m I hadn&#8217;t looked at for a bit: wireless mouse handling.</p>
<p>I thought this was broken, but it&#8217;s actually not &#8211; if I plug in a wireless mouse and set the icon policy to &#8216;always&#8217;, I get an icon in the notification area which tells me the charge level of the mouse. Shiny. But the icon doesn&#8217;t show up if the icon policy is set to &#8216;present&#8217; &#8211; I guess that only considers the presence of a laptop battery, not any other kind of battery&#8230;</p>
<p>Also, gnome-power-preferences only lets you set the &#8216;always&#8217; or &#8216;never&#8217; policies for the icon. That seems somewhat over-simplified. I can&#8217;t see why the UI shouldn&#8217;t expose the other choices too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
