<?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"
	>
<channel>
	<title>Comments on: Virtual Keys</title>
	<atom:link href="http://blakeseely.com/blog/archives/2006/09/26/virtual-keys/feed/" rel="self" type="application/rss+xml" />
	<link>http://blakeseely.com/blog/archives/2006/09/26/virtual-keys/</link>
	<description>If I could put reflection under this header, I would.</description>
	<pubDate>Wed, 20 Aug 2008 20:26:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Peter Maurer</title>
		<link>http://blakeseely.com/blog/archives/2006/09/26/virtual-keys/#comment-13311</link>
		<dc:creator>Peter Maurer</dc:creator>
		<pubDate>Thu, 28 Sep 2006 07:57:38 +0000</pubDate>
		<guid isPermaLink="false">http://blakeseely.com/blog/archives/2006/09/26/virtual-keys/#comment-13311</guid>
		<description>There's one possible use for virtual key codes you forgot to mention: simulating keystrokes. This is something a lot of applications do -- e.g., those applications that use the clipboard for inserting content by simulating a [command]-[v] keystroke.

While that's not a perfect approach -- given the editability of keyboard shortcuts such as [command]-[v] -- it is indeed a wide-spread way of triggering a paste action. And it's the most reliable way of doing so I'm aware of.

The interesting part here is that most developers tend to forget what you've mentioned near the beginning of your article: The [v] key isn't always in the same place, and it might even change its position depending on the modifier key state. Think Dvorak-Qwerty. Unfortunately, finding out the virtual key code for a given character during runtime is not fun on Mac OS.

It took me a while to find a way around these problems when I was faced with them for the first time; and I just wanted to say "thank you" for the memories.</description>
		<content:encoded><![CDATA[<p>There&#8217;s one possible use for virtual key codes you forgot to mention: simulating keystrokes. This is something a lot of applications do &#8212; e.g., those applications that use the clipboard for inserting content by simulating a [command]-[v] keystroke.</p>
<p>While that&#8217;s not a perfect approach &#8212; given the editability of keyboard shortcuts such as [command]-[v] &#8212; it is indeed a wide-spread way of triggering a paste action. And it&#8217;s the most reliable way of doing so I&#8217;m aware of.</p>
<p>The interesting part here is that most developers tend to forget what you&#8217;ve mentioned near the beginning of your article: The [v] key isn&#8217;t always in the same place, and it might even change its position depending on the modifier key state. Think Dvorak-Qwerty. Unfortunately, finding out the virtual key code for a given character during runtime is not fun on Mac OS.</p>
<p>It took me a while to find a way around these problems when I was faced with them for the first time; and I just wanted to say &#8220;thank you&#8221; for the memories.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
