<?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: A Dim View of Menus</title>
	<atom:link href="http://blog.wilsonet.com/archives/2004/05/30/a-dim-view-of-menus/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wilsonet.com/archives/2004/05/30/a-dim-view-of-menus/</link>
	<description>Interaction and interface design, technology, politics, music, and random thoughts...</description>
	<lastBuildDate>Mon, 12 Dec 2011 18:22:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Buzz Andersen</title>
		<link>http://blog.wilsonet.com/archives/2004/05/30/a-dim-view-of-menus/comment-page-1/#comment-158</link>
		<dc:creator>Buzz Andersen</dc:creator>
		<pubDate>Wed, 02 Jun 2004 06:42:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wilsonet.com/wp-login.php/wp-admin/archives/category/meta-data/archives/category/wp-images/smilies/feed/wp-images/smilies/archives/2004/02/16/wp-images/smilies/archives/2004/02/03/archives/2003/11/01/feed/archives/2004/02/archives/2004/05/30/a#comment-158</guid>
		<description>Man, you&#039;re just full of ideas :-).  I&#039;ll try to suggest that to the appropriate parties as well (just as soon as I figure out who they are).</description>
		<content:encoded><![CDATA[<p>Man, you&#8217;re just full of ideas :-).  I&#8217;ll try to suggest that to the appropriate parties as well (just as soon as I figure out who they are).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel J. Wilson</title>
		<link>http://blog.wilsonet.com/archives/2004/05/30/a-dim-view-of-menus/comment-page-1/#comment-157</link>
		<dc:creator>Daniel J. Wilson</dc:creator>
		<pubDate>Wed, 02 Jun 2004 05:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wilsonet.com/wp-login.php/wp-admin/archives/category/meta-data/archives/category/wp-images/smilies/feed/wp-images/smilies/archives/2004/02/16/wp-images/smilies/archives/2004/02/03/archives/2003/11/01/feed/archives/2004/02/archives/2004/05/30/a#comment-157</guid>
		<description>Thanks for the info!  I&#039;d wondered if it was simply that applications (Cocoa in particular) just didn&#039;t automatically dim unavailable menu bar and sub-menu titles.  Menu dimming is a small thing, but when it is done properly it can make it a lot easier to find commands that are usable at a given point.  I&#039;ll send in a comment about it as well.

Your unawareness of the dimming guidelines gives me another idea!  How about HIG syndication feeds?</description>
		<content:encoded><![CDATA[<p>Thanks for the info!  I&#8217;d wondered if it was simply that applications (Cocoa in particular) just didn&#8217;t automatically dim unavailable menu bar and sub-menu titles.  Menu dimming is a small thing, but when it is done properly it can make it a lot easier to find commands that are usable at a given point.  I&#8217;ll send in a comment about it as well.</p>
<p>Your unawareness of the dimming guidelines gives me another idea!  How about HIG syndication feeds?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Buzz Andersen</title>
		<link>http://blog.wilsonet.com/archives/2004/05/30/a-dim-view-of-menus/comment-page-1/#comment-156</link>
		<dc:creator>Buzz Andersen</dc:creator>
		<pubDate>Wed, 02 Jun 2004 02:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wilsonet.com/wp-login.php/wp-admin/archives/category/meta-data/archives/category/wp-images/smilies/feed/wp-images/smilies/archives/2004/02/16/wp-images/smilies/archives/2004/02/03/archives/2003/11/01/feed/archives/2004/02/archives/2004/05/30/a#comment-156</guid>
		<description>To answer your question about the technical aspects of menu validation, essentially the way it works for Cocoa applications is that each time through the event loop (in other words, each time an event is triggered by a mouse click or whatever), the target object for each menu item is asked whether the menu item is currently valid.  This is *not* done for entire menus, however, which would explain why none of the Cocoa apps you mention actually adhere to that guideline (iTunes is a Carbon app, and Carbon apps have a different way of handling menus).  It is possible to do what you&#039;re talking about in Cocoa, it&#039;s just not part of the &quot;normal&quot; way of doing things.

I never thought about it (I wasn&#039;t aware of the guideline to be honest), but you bring up an excellent point.  I&#039;ll file a bug suggesting that Cocoa menu validation should also handle whole menus.</description>
		<content:encoded><![CDATA[<p>To answer your question about the technical aspects of menu validation, essentially the way it works for Cocoa applications is that each time through the event loop (in other words, each time an event is triggered by a mouse click or whatever), the target object for each menu item is asked whether the menu item is currently valid.  This is *not* done for entire menus, however, which would explain why none of the Cocoa apps you mention actually adhere to that guideline (iTunes is a Carbon app, and Carbon apps have a different way of handling menus).  It is possible to do what you&#8217;re talking about in Cocoa, it&#8217;s just not part of the &#8220;normal&#8221; way of doing things.</p>
<p>I never thought about it (I wasn&#8217;t aware of the guideline to be honest), but you bring up an excellent point.  I&#8217;ll file a bug suggesting that Cocoa menu validation should also handle whole menus.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

