<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Inhibit and ForceInhibit</title>
	<link>http://blogs.gnome.org/hughsie/2007/01/31/inhibit-and-forceinhibit/</link>
	<description>My fiancee is like Windows Vista: Looks pretty, difficult to understand and sometimes unpredictable...</description>
	<pubDate>Thu, 28 Aug 2008 12:15:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Anonymous</title>
		<link>http://blogs.gnome.org/hughsie/2007/01/31/inhibit-and-forceinhibit/#comment-43</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 31 Jan 2007 18:03:43 +0000</pubDate>
		<guid>http://blogs.gnome.org/hughsie/2007/01/31/inhibit-and-forceinhibit/#comment-43</guid>
		<description>One thing that could help solve that bug would be to allow a dialog to pop up and explain why a (intentional?) action was inhibit.  This dialog could provide options like "Cancel Suspend", "Pause file transfer and continue to suspend" or "Make me a new coaster and stop burning now"</description>
		<content:encoded><![CDATA[<p>One thing that could help solve that bug would be to allow a dialog to pop up and explain why a (intentional?) action was inhibit.  This dialog could provide options like &#8220;Cancel Suspend&#8221;, &#8220;Pause file transfer and continue to suspend&#8221; or &#8220;Make me a new coaster and stop burning now&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
