taming the cursor

[joe.user0]

Hello,
I have a text application in C that works well on
quick machines. On old PCs, I have to press and
release the arrow keys slowly. If I push and keep
an arrow key down, the cursor goes wild and lands
somewhere without any understandable pattern.

I need an idea - or some code - for the following:

after executing a command, discard the same
command if it comes within x milliseconds.
Thanks.
Joe

[Alexander Bartolich]

jo*******@lycos.com wrote:

I have a text application in C that works well on
quick machines. On old PCs, I have to press and
release the arrow keys slowly. If I push and keep
an arrow key down, the cursor goes wild and lands
somewhere without any understandable pattern.
This is platform specific and thus off-topic.
I need an idea - or some code - for the following:

after executing a command, discard the same
command if it comes within x milliseconds.

Well, on some systems you can detect the events key-press and
key-release independently. Triggering on release would be a
simple workaround.

Anyway, the only way to measure time with a resolution below
one second is clock().

[Keith Thompson]

Alexander Bartolich <al*****************@gmx.at> writes:
[...]

Anyway, the only way to measure time with a resolution below
one second is clock().

Um, not really. clock() measures CPU time, not real time. The
resolution of the time() function is commonly 1 second, but the
standard doesn't guarantee this.

Practically speaking, the only way to measure time with a resolution
below one second is to use some system-specific extension.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.