<?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: When to make an action Invisible or Disabled</title>
	<atom:link href="http://www.danrigsby.com/blog/index.php/2008/05/02/when-to-make-an-action-invisible-or-disabled/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.danrigsby.com/blog/index.php/2008/05/02/when-to-make-an-action-invisible-or-disabled/</link>
	<description>Developer.Speaker.Blogger</description>
	<lastBuildDate>Sun, 14 Aug 2011 06:09:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Hall</title>
		<link>http://www.danrigsby.com/blog/index.php/2008/05/02/when-to-make-an-action-invisible-or-disabled/comment-page-1/#comment-508</link>
		<dc:creator>Mike Hall</dc:creator>
		<pubDate>Mon, 05 May 2008 02:20:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.danrigsby.com/blog/?p=201#comment-508</guid>
		<description>As opposed to the user having permission, I usually state that something should be invisible if the user can never enable the option. It should be disabled if the user can at some point enable that option. This may involve having permission, or may involve something else like the a file is locked or the time of day or whatever.

On a similar note is whether a control should be disabled or not if the user can activate that control on the same page/dialog or if they need to go somewhere else to activate it. If they can&#039;t activate it on the same page, the user may get frustrated trying to figure out what they need to check or change to activate the control. But sometimes, you just can&#039;t help that either.</description>
		<content:encoded><![CDATA[<p>As opposed to the user having permission, I usually state that something should be invisible if the user can never enable the option. It should be disabled if the user can at some point enable that option. This may involve having permission, or may involve something else like the a file is locked or the time of day or whatever.</p>
<p>On a similar note is whether a control should be disabled or not if the user can activate that control on the same page/dialog or if they need to go somewhere else to activate it. If they can&#8217;t activate it on the same page, the user may get frustrated trying to figure out what they need to check or change to activate the control. But sometimes, you just can&#8217;t help that either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dew Drop - May 3, 2008 &#124; Alvin Ashcraft's Morning Dew</title>
		<link>http://www.danrigsby.com/blog/index.php/2008/05/02/when-to-make-an-action-invisible-or-disabled/comment-page-1/#comment-495</link>
		<dc:creator>Dew Drop - May 3, 2008 &#124; Alvin Ashcraft's Morning Dew</dc:creator>
		<pubDate>Sat, 03 May 2008 16:00:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.danrigsby.com/blog/?p=201#comment-495</guid>
		<description>[...] When to Make an Action Invisible or Disabled (Dan Rigsby) [...]</description>
		<content:encoded><![CDATA[<p>[...] When to Make an Action Invisible or Disabled (Dan Rigsby) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

