<?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: John Gruber on anchored and unanchored selection in lists and text views in Mac OS X</title>
	<atom:link href="http://www.betalogue.com/2006/08/05/john-gruber-on-anchored-and-unanchored-selection-in-lists-and-text-views-in-mac-os-x/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.betalogue.com/2006/08/05/john-gruber-on-anchored-and-unanchored-selection-in-lists-and-text-views-in-mac-os-x/</link>
	<description>Notes from an unfinished world…</description>
	<lastBuildDate>Sat, 18 Feb 2012 11:48:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: ssp</title>
		<link>http://www.betalogue.com/2006/08/05/john-gruber-on-anchored-and-unanchored-selection-in-lists-and-text-views-in-mac-os-x/comment-page-1/#comment-6283</link>
		<dc:creator>ssp</dc:creator>
		<pubDate>Sun, 06 Aug 2006 16:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.betalogue.com/2006/08/05/john-gruber-on-anchored-and-unanchored-selection-in-lists-and-text-views-in-mac-os-x/#comment-6283</guid>
		<description>I&#039;m really split on this one. John Gruber does make a good point and the effort of explaining what&#039;s going on and why. 

Not being a frequent keyboard-list-selector myself, I have still managed to run into this exact problem and consider it a problem. Yet, I keep thinking the implemented behaviour is quite logical and easier to understand than the behaviour that may come handy in some situations. Particularly so as the current way Apple handle this issue leaves no ambiguities: You see that screen and whatever single, multiple or discontinuous selection you have it is clear and predictable what hitting a shift-arrow key combination will do. 

So this comes down to a fight between clarity and predictability vs an easy way (for geeks, as you point out) to correct their typos. And while I may have suffered from this &#039;problem&#039; myself, I generally think that Apple siding with clarity and predictability is both consistent and a good thing.</description>
		<content:encoded><![CDATA[<p>I&#8217;m really split on this one. John Gruber does make a good point and the effort of explaining what&#8217;s going on and why. </p>
<p>Not being a frequent keyboard-list-selector myself, I have still managed to run into this exact problem and consider it a problem. Yet, I keep thinking the implemented behaviour is quite logical and easier to understand than the behaviour that may come handy in some situations. Particularly so as the current way Apple handle this issue leaves no ambiguities: You see that screen and whatever single, multiple or discontinuous selection you have it is clear and predictable what hitting a shift-arrow key combination will do. </p>
<p>So this comes down to a fight between clarity and predictability vs an easy way (for geeks, as you point out) to correct their typos. And while I may have suffered from this &#8216;problem&#8217; myself, I generally think that Apple siding with clarity and predictability is both consistent and a good thing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

