<?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: On Anchored Selections in Windows, Gnome, and Mac&#160;OS&#160;X</title>
	<atom:link href="http://www.codingrobots.com/blog/2009/04/28/selections/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codingrobots.com/blog/2009/04/28/selections/</link>
	<description>In bytes we trust</description>
	<lastBuildDate>Fri, 06 Jan 2012 23:40:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Matt Dietsche</title>
		<link>http://www.codingrobots.com/blog/2009/04/28/selections/comment-page-1/#comment-2557</link>
		<dc:creator>Matt Dietsche</dc:creator>
		<pubDate>Thu, 18 Jun 2009 15:25:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.codingrobots.com/?p=1450#comment-2557</guid>
		<description>&lt;p&gt;Hey, wondering if anyone knows of a mac app that allows me to hijack the MacOSX text select parameters.  I deal with a lot of copying and pasting of code and customer passwords that contain dashes, underscores and various punctuation.  I would love to have double-clicking on text select everything between spaces, instead of breaking at punctuation.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hey, wondering if anyone knows of a mac app that allows me to hijack the MacOSX text select parameters.  I deal with a lot of copying and pasting of code and customer passwords that contain dashes, underscores and various punctuation.  I would love to have double-clicking on text select everything between spaces, instead of breaking at punctuation.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Mayes</title>
		<link>http://www.codingrobots.com/blog/2009/04/28/selections/comment-page-1/#comment-2461</link>
		<dc:creator>Luke Mayes</dc:creator>
		<pubDate>Fri, 01 May 2009 00:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.codingrobots.com/?p=1450#comment-2461</guid>
		<description>&lt;p&gt;Thanks for the explanation of Cocoa&#039;s. Text selection on my mac now makes sense to me. List selection, of course, is another story. How does growing a selection in both directions (like in iTunes) ever make sense? What is a scenario where that behavior is useful?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks for the explanation of Cocoa&#8217;s. Text selection on my mac now makes sense to me. List selection, of course, is another story. How does growing a selection in both directions (like in iTunes) ever make sense? What is a scenario where that behavior is useful?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Rasmussen</title>
		<link>http://www.codingrobots.com/blog/2009/04/28/selections/comment-page-1/#comment-2459</link>
		<dc:creator>Daniel Rasmussen</dc:creator>
		<pubDate>Thu, 30 Apr 2009 12:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.codingrobots.com/?p=1450#comment-2459</guid>
		<description>&lt;p&gt;Leish, both are Cocoa, and TextEdit&#039;s behavior is how a Cocoa app would behave if it used the standard Apple-provided controls. Safari&#039;s behavior is a incorrect, presumably due to it being implemented differently.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Leish, both are Cocoa, and TextEdit&#8217;s behavior is how a Cocoa app would behave if it used the standard Apple-provided controls. Safari&#8217;s behavior is a incorrect, presumably due to it being implemented differently.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.codingrobots.com/blog/2009/04/28/selections/comment-page-1/#comment-2458</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 30 Apr 2009 09:34:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.codingrobots.com/?p=1450#comment-2458</guid>
		<description>&lt;p&gt;I&#039;ve been liking the way my mac uses the text selection, as I often find especially in Word in Windows that the whole word selection seems rather clumsy, especially when all I want to get us part of a long URL, or a small segment of a longer word. Aslo being left haded, I usually drag from right to left.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been liking the way my mac uses the text selection, as I often find especially in Word in Windows that the whole word selection seems rather clumsy, especially when all I want to get us part of a long URL, or a small segment of a longer word. Aslo being left haded, I usually drag from right to left.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Wise</title>
		<link>http://www.codingrobots.com/blog/2009/04/28/selections/comment-page-1/#comment-2457</link>
		<dc:creator>Mark Wise</dc:creator>
		<pubDate>Wed, 29 Apr 2009 15:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.codingrobots.com/?p=1450#comment-2457</guid>
		<description>&lt;p&gt;List selection in Leopard drives me batty!&lt;/p&gt;

&lt;p&gt;If I use shift+down to select a list in Finder, shift+up should =deselect= the last item rather than adding an item above the anchor.&lt;/p&gt;

&lt;p&gt;Move down one, up reverses that.  How...novel.  Grrrrr!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>List selection in Leopard drives me batty!</p>

<p>If I use shift+down to select a list in Finder, shift+up should =deselect= the last item rather than adding an item above the anchor.</p>

<p>Move down one, up reverses that.  How&#8230;novel.  Grrrrr!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: foljs</title>
		<link>http://www.codingrobots.com/blog/2009/04/28/selections/comment-page-1/#comment-2452</link>
		<dc:creator>foljs</dc:creator>
		<pubDate>Wed, 29 Apr 2009 10:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.codingrobots.com/?p=1450#comment-2452</guid>
		<description>&lt;p&gt;@Igot&lt;/p&gt;

&lt;p&gt;&lt;b&gt;There is no reason why there should be an inconsistency. Yet more mental adjustments required all the time.&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;If those are the kind of &quot;mental adjustments&quot; you have to do in your workflow, then Apple did a truly truly deeply fine job.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Igot</p>

<p><b>There is no reason why there should be an inconsistency. Yet more mental adjustments required all the time.</b></p>

<p>If those are the kind of &#8220;mental adjustments&#8221; you have to do in your workflow, then Apple did a truly truly deeply fine job.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: pinchies</title>
		<link>http://www.codingrobots.com/blog/2009/04/28/selections/comment-page-1/#comment-2451</link>
		<dc:creator>pinchies</dc:creator>
		<pubDate>Wed, 29 Apr 2009 09:19:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.codingrobots.com/?p=1450#comment-2451</guid>
		<description>&lt;p&gt;@Leigh
If you add in the control and option keys while selecting using shift and the arrow keys, you can get even more options with odd actions.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Leigh
If you add in the control and option keys while selecting using shift and the arrow keys, you can get even more options with odd actions.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: pwb</title>
		<link>http://www.codingrobots.com/blog/2009/04/28/selections/comment-page-1/#comment-2449</link>
		<dc:creator>pwb</dc:creator>
		<pubDate>Wed, 29 Apr 2009 00:53:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.codingrobots.com/?p=1450#comment-2449</guid>
		<description>&lt;p&gt;&quot;placing anchor to the end of your selection is the right way. But this logic is flawed. It’s no harder to miss a character when you begin selecting text, than to miss it when you finish&quot;&lt;/p&gt;

&lt;p&gt;Wrong. It&#039;s not about correcting missed characters. It&#039;s about what makes sense!!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><span class="dquo">&#8220;</span>placing anchor to the end of your selection is the right way. But this logic is flawed. It’s no harder to miss a character when you begin selecting text, than to miss it when you finish&#8221;</p>

<p>Wrong. It&#8217;s not about correcting missed characters. It&#8217;s about what makes sense!!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Leish2</title>
		<link>http://www.codingrobots.com/blog/2009/04/28/selections/comment-page-1/#comment-2447</link>
		<dc:creator>Leish2</dc:creator>
		<pubDate>Wed, 29 Apr 2009 00:40:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.codingrobots.com/?p=1450#comment-2447</guid>
		<description>&lt;p&gt;In Safari Beta 4 on OS X 10.5.6 - I presume this is cocoa but I could well be wrong:
• If you select-drag text then shift+arrow selects more text in the direction of the arrow.
• If you double click to select a single word then shift+arrow selects more text in the direction of the arrow starting from the EXACT point of the cursor when double clicking.
• triple click selects a paragraph and then shift+arrow selects more text in the direction of the arrow starting from the EXACT point of the cursor when triple clicking.&lt;/p&gt;

&lt;p&gt;In TextEdit - which I guess is not Cocoa since it behaves differently than Safari but I could be wrong:
• If you select-drag text then shift+arrow selects more text in the direction of the arrow.
• If you double click to select a single word then shift+arrow selects more text in the direction of the arrow.
• triple click selects a paragraph and then shift+arrow selects more text in the direction of the arrow.&lt;/p&gt;

&lt;p&gt;I like the way TextEdit workst Safari could be different due to the nature of HTML - I have no idea really.&lt;/p&gt;

&lt;p&gt;Cheers, Leish&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>In Safari Beta 4 on OS X 10.5.6 - I presume this is cocoa but I could well be wrong:
• If you select-drag text then shift+arrow selects more text in the direction of the arrow.
• If you double click to select a single word then shift+arrow selects more text in the direction of the arrow starting from the EXACT point of the cursor when double clicking.
• triple click selects a paragraph and then shift+arrow selects more text in the direction of the arrow starting from the EXACT point of the cursor when triple clicking.</p>

<p>In TextEdit - which I guess is not Cocoa since it behaves differently than Safari but I could be wrong:
• If you select-drag text then shift+arrow selects more text in the direction of the arrow.
• If you double click to select a single word then shift+arrow selects more text in the direction of the arrow.
• triple click selects a paragraph and then shift+arrow selects more text in the direction of the arrow.</p>

<p>I like the way TextEdit workst Safari could be different due to the nature of HTML - I have no idea really.</p>

<p>Cheers, Leish</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre Igot</title>
		<link>http://www.codingrobots.com/blog/2009/04/28/selections/comment-page-1/#comment-2444</link>
		<dc:creator>Pierre Igot</dc:creator>
		<pubDate>Tue, 28 Apr 2009 17:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.codingrobots.com/?p=1450#comment-2444</guid>
		<description>&lt;p&gt;As indicated in my post, the most frustrating aspect of all this is the unpredictability. Maybe one day all Apple applications and even all Mac OS X applications will behave the same way, but until that day, having to constantly adjust one&#039;s habits depending on which application one is using will remain frustrating.&lt;/p&gt;

&lt;p&gt;And your lack of explanation of the inconsistency between text selection and list selection illustrates another aspect of the problem, which is that it does not appear to have been thought through. There is no reason why there should be an inconsistency. Yet more mental adjustments required all the time.&lt;/p&gt;

&lt;p&gt;In answer to your explanation itself, I would argue that users probably focus more on the accuracy of their clicking for the beginning of the selection as opposed to the end, for the simple reason that it&#039;s more difficult to be accurate when one of your hand&#039;s fingers is pressing on a mouse button (i.e. while dragging). The initial click is probably more accurate simply because there is no tension in the hand resulting from having to press on something.&lt;/p&gt;

&lt;p&gt;This would have to be backed up by actual scientific evidence, of course, but I do wonder whether it has even been considered by whoever made the decision to remove anchoring in Cocoa.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>As indicated in my post, the most frustrating aspect of all this is the unpredictability. Maybe one day all Apple applications and even all Mac OS X applications will behave the same way, but until that day, having to constantly adjust one&#8217;s habits depending on which application one is using will remain frustrating.</p>

<p>And your lack of explanation of the inconsistency between text selection and list selection illustrates another aspect of the problem, which is that it does not appear to have been thought through. There is no reason why there should be an inconsistency. Yet more mental adjustments required all the time.</p>

<p>In answer to your explanation itself, I would argue that users probably focus more on the accuracy of their clicking for the beginning of the selection as opposed to the end, for the simple reason that it&#8217;s more difficult to be accurate when one of your hand&#8217;s fingers is pressing on a mouse button (i.e. while dragging). The initial click is probably more accurate simply because there is no tension in the hand resulting from having to press on something.</p>

<p>This would have to be backed up by actual scientific evidence, of course, but I do wonder whether it has even been considered by whoever made the decision to remove anchoring in Cocoa.</p>]]></content:encoded>
	</item>
</channel>
</rss>

