<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Capturing keystrokes with GetAsyncKeyState</title>
	<link>http://coding.moris.org/archives/2003/11/05/capturing-keystrokes-with-getasynckeystate/</link>
	<description>Java programming tips and advice, and other topics</description>
	<pubDate>Thu, 09 Sep 2010 20:52:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Markus M�ller</title>
		<link>http://coding.moris.org/archives/2003/11/05/capturing-keystrokes-with-getasynckeystate/#comment-41</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://coding.moris.org/archives/2003/11/05/capturing-keystrokes-with-getasynckeystate/#comment-41</guid>
					<description>What, if I hit the keys faster than timers interval? Even if the interval is 1, it seems to be possible to hit faster. So the function misses some keys :-(

Does anybody know, how to solve this problem?

Greets :-)</description>
		<content:encoded><![CDATA[<p>What, if I hit the keys faster than timers interval? Even if the interval is 1, it seems to be possible to hit faster. So the function misses some keys :-(</p>
<p>Does anybody know, how to solve this problem?</p>
<p>Greets :-)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eddy Young</title>
		<link>http://coding.moris.org/archives/2003/11/05/capturing-keystrokes-with-getasynckeystate/#comment-42</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://coding.moris.org/archives/2003/11/05/capturing-keystrokes-with-getasynckeystate/#comment-42</guid>
					<description>Sometimes a higher interval is preferable so as not to overload the system with unnecessary checks. 100 ms seems to work for me with insignificant misses.</description>
		<content:encoded><![CDATA[<p>Sometimes a higher interval is preferable so as not to overload the system with unnecessary checks. 100 ms seems to work for me with insignificant misses.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Markus M�ller</title>
		<link>http://coding.moris.org/archives/2003/11/05/capturing-keystrokes-with-getasynckeystate/#comment-43</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://coding.moris.org/archives/2003/11/05/capturing-keystrokes-with-getasynckeystate/#comment-43</guid>
					<description>Ok, the timer is fast enough and could be about 100ms. But my event, that starts at some special keys, runs round about one second (!)
So every key, I hit in the meantime, is not realized. It would be nice to have an input-queue. Is this supported by windows? Or do I have to build the queue by myself?

Markus</description>
		<content:encoded><![CDATA[<p>Ok, the timer is fast enough and could be about 100ms. But my event, that starts at some special keys, runs round about one second (!)<br />
So every key, I hit in the meantime, is not realized. It would be nice to have an input-queue. Is this supported by windows? Or do I have to build the queue by myself?</p>
<p>Markus
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eddy Young</title>
		<link>http://coding.moris.org/archives/2003/11/05/capturing-keystrokes-with-getasynckeystate/#comment-44</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://coding.moris.org/archives/2003/11/05/capturing-keystrokes-with-getasynckeystate/#comment-44</guid>
					<description>Building a queue should not be a hard job. Just use the FIFO principle to add and remove keystrokes from your queue.</description>
		<content:encoded><![CDATA[<p>Building a queue should not be a hard job. Just use the FIFO principle to add and remove keystrokes from your queue.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
