<?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: Tab through layers to rename them in CS6</title>
	<atom:link href="http://blogs.adobe.com/jnack/2012/06/tab-through-layers-to-rename-them-in-cs6.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2012/06/tab-through-layers-to-rename-them-in-cs6.html</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 04:53:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Adam Norwood</title>
		<link>http://blogs.adobe.com/jnack/2012/06/tab-through-layers-to-rename-them-in-cs6.html#comment-44966</link>
		<dc:creator>Adam Norwood</dc:creator>
		<pubDate>Mon, 04 Jun 2012 20:38:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=6829#comment-44966</guid>
		<description><![CDATA[John: if you have access to your WordPress theme, you might check in comments.php (or wherever your comment form is defined) to see if you can edit out the tabindex attributes that are added to each input box -- they conflict with the numbers already defined up in the &quot;skip links&quot; part of your header. Tabindex is a good accessibility idea in theory, but it&#039;s often guilty of leading to further accessibility problems :) (see here for more: http://webaim.org/techniques/keyboard/tabindex)]]></description>
		<content:encoded><![CDATA[<p>John: if you have access to your WordPress theme, you might check in comments.php (or wherever your comment form is defined) to see if you can edit out the tabindex attributes that are added to each input box &#8212; they conflict with the numbers already defined up in the &#8220;skip links&#8221; part of your header. Tabindex is a good accessibility idea in theory, but it&#8217;s often guilty of leading to further accessibility problems :) (see here for more: <a href="http://webaim.org/techniques/keyboard/tabindex" rel="nofollow">http://webaim.org/techniques/keyboard/tabindex</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Norwood</title>
		<link>http://blogs.adobe.com/jnack/2012/06/tab-through-layers-to-rename-them-in-cs6.html#comment-44947</link>
		<dc:creator>Adam Norwood</dc:creator>
		<pubDate>Mon, 04 Jun 2012 15:53:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=6829#comment-44947</guid>
		<description><![CDATA[Yes! This is one of those small features that I didn&#039;t know that I needed, exactly, but has already been very useful. 

If you&#039;re like me and use keyboard shortcuts as much as possible I&#039;d suggest mapping a new shortcut to the &quot;Layer &gt; Rename Layer…&quot; menu item, which makes the process even easier (I&#039;ve mapped it to the F2 key to mimic the file rename shortcut in Windows, but YMMV).

(Ironically-related PS: I was using TAB to enter my info in this comment form, and it kept bouncing me to the top of your page – looks like there are duplicated / conflicting tabindex attributes in the HTML?)

&lt;i&gt;[Yeah, I know, but I don&#039;t know how to fix it. Suggestions would be most welcome.  --J.]&lt;/i&gt; ]]></description>
		<content:encoded><![CDATA[<p>Yes! This is one of those small features that I didn&#8217;t know that I needed, exactly, but has already been very useful. </p>
<p>If you&#8217;re like me and use keyboard shortcuts as much as possible I&#8217;d suggest mapping a new shortcut to the &#8220;Layer &gt; Rename Layer…&#8221; menu item, which makes the process even easier (I&#8217;ve mapped it to the F2 key to mimic the file rename shortcut in Windows, but YMMV).</p>
<p>(Ironically-related PS: I was using TAB to enter my info in this comment form, and it kept bouncing me to the top of your page – looks like there are duplicated / conflicting tabindex attributes in the HTML?)</p>
<p><i>[Yeah, I know, but I don't know how to fix it. Suggestions would be most welcome.  --J.]</i> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken</title>
		<link>http://blogs.adobe.com/jnack/2012/06/tab-through-layers-to-rename-them-in-cs6.html#comment-44939</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Mon, 04 Jun 2012 14:23:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=6829#comment-44939</guid>
		<description><![CDATA[Morning John,

I just found the &quot;oil paint&quot; feature in CS6.

Some of your readers might like a background I created with this application.

http://500px.com/photo/8256071

Really adds a lot of &quot;punch&quot; to walls

Ken in Kentucky]]></description>
		<content:encoded><![CDATA[<p>Morning John,</p>
<p>I just found the &#8220;oil paint&#8221; feature in CS6.</p>
<p>Some of your readers might like a background I created with this application.</p>
<p><a href="http://500px.com/photo/8256071" rel="nofollow">http://500px.com/photo/8256071</a></p>
<p>Really adds a lot of &#8220;punch&#8221; to walls</p>
<p>Ken in Kentucky</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trent</title>
		<link>http://blogs.adobe.com/jnack/2012/06/tab-through-layers-to-rename-them-in-cs6.html#comment-44937</link>
		<dc:creator>Trent</dc:creator>
		<pubDate>Mon, 04 Jun 2012 14:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=6829#comment-44937</guid>
		<description><![CDATA[In reference to your comment &quot;Details count&quot;.  I&#039;ve been complaining since PS3 about the inability to have larger IU menus in photoshop for those of us who have large (30&quot;) monitors and want to use the max resolution (2560 x 1600) but have to break up their workflow by having to lean forward towards the monitor, with computer glasses, to read the toolbar.  Not fair!  Examples at the forum

http://forums.adobe.com/message/4421267#4421267

&lt;i&gt;[Support for resolution-independent (scalable) UI is a must. It&#039;s just a question of &quot;when,&quot; not &quot;if.&quot;  --J.]&lt;/i&gt; ]]></description>
		<content:encoded><![CDATA[<p>In reference to your comment &#8220;Details count&#8221;.  I&#8217;ve been complaining since PS3 about the inability to have larger IU menus in photoshop for those of us who have large (30&#8243;) monitors and want to use the max resolution (2560 x 1600) but have to break up their workflow by having to lean forward towards the monitor, with computer glasses, to read the toolbar.  Not fair!  Examples at the forum</p>
<p><a href="http://forums.adobe.com/message/4421267#4421267" rel="nofollow">http://forums.adobe.com/message/4421267#4421267</a></p>
<p><i>[Support for resolution-independent (scalable) UI is a must. It's just a question of "when," not "if."  --J.]</i> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Herman van Boeijen</title>
		<link>http://blogs.adobe.com/jnack/2012/06/tab-through-layers-to-rename-them-in-cs6.html#comment-44910</link>
		<dc:creator>Herman van Boeijen</dc:creator>
		<pubDate>Sun, 03 Jun 2012 23:25:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=6829#comment-44910</guid>
		<description><![CDATA[I personally appreciate the hell out of this!
The combination with the search function is especially powerful! (though I did encounter a wee bug with a program error when I tabbed from an item leaving it not-matching the filter) 

Don&#039;t forget the crown jewel: no more &quot;copy of&quot; on layers! :) !

If only the same person that took care of these things would look at the undo/redo/layer change interaction... ;)]]></description>
		<content:encoded><![CDATA[<p>I personally appreciate the hell out of this!<br />
The combination with the search function is especially powerful! (though I did encounter a wee bug with a program error when I tabbed from an item leaving it not-matching the filter) </p>
<p>Don&#8217;t forget the crown jewel: no more &#8220;copy of&#8221; on layers! :) !</p>
<p>If only the same person that took care of these things would look at the undo/redo/layer change interaction&#8230; ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
