From: Ross_Boyd@tnt.com.au
G'day Chris,
Chris wrote:
>CodeWright does this by intentionally misinterpreting keystrokes.  a
>console mode app cannot do this, but a fully GUI app can.  technical
>info follows...
>keystrokes are received as messages that say which key was pressed,
>whether is is being pressed (eg, WM_KEYDOWN & others), or released
>(WM_KEYUP & others), and also how many times the key has been pressed
>(if the system is very busy and the user is holding down a key,
>keypressed can be "batched" by a WM_KEYDOWN that says "8 presses", >etc).
>that's a simplified explanation, but good enough to explain how
>Codewright does it.  so Codewright detects when a key is being held (ie,
>a WM_KEYDOWN has come, but no WM_KEYUP yet) and will start to multiply
>the keystrokes.  so if you hold a key down for 5 seconds, Windows may
>tell Codewright that the key has been hit 20 times, but Codewright can
>"accelerate" the keyboard by multiplying and behaving as if the key were
>pressed 40 times, etc.
> chris
Thanks for clarifying that.
I've used this technique in my own (DOS) applications to speed up 
scrolling of pages of displayed text. So I know what you mean.
It seems like it would be pretty simple to implement in TSE Pro for Windows.
Hmmmm... yoohooo Sammy .
Seriously though, I'm about to d/l and try the qkeys macro that Sammy 
has ported to 32bit. That uses the same technique. It didn't accelerate 
the keyrate anywhere near what I'd like in TSE 2.5. Maybe all it needs 
is the ability to configure the repeatrate and delay.
BTW, did you ever try Hyperkey (a shareware DOS TSR)? It worked very 
well with TSE 2.5.  It felt like TSE was turbo-charged!
Anyway, I'm gonna try qkeys and see if that will do the trick. Thanks 
for all your info.
Regards,
Ross Boyd 	

---
---------------