News:

MASM32 SDK Description, downloads and other helpful links
MASM32.com New Forum Link
masmforum WebSite

Keyboard State

Started by MicronXD, December 01, 2007, 10:43:11 AM

Previous topic - Next topic
Print
Go Down Pages1
User actions

MicronXD

December 01, 2007, 10:43:11 AM
MS Windows XP seems to have a seperate keyboard buffer for each process that checks for keys. The problem with that is, I need a way to capture keys and check the sequence even if the charactors type are going into notepad. I'm not sure the way I'm explaining it is completely clear, so I'll explain what it is I'm trying to do :P

I'm trying to make a small app that will open it's GUI when the user types [ctrl], [windows key], [alt], [space]... However, what was supposed to be a BIOS level interupt is caught by MS Windows, and blocks me from catching the keys when Windows's focus is on notepad or any other program.

I know it's possible, because its done in keyloggers, Launchy (awesome lil app you all should get), and a few other places. So any suggestions?

MichaelW

#2
December 01, 2007, 12:06:16 PM
QuoteI'm trying to make a small app that will open it's GUI when the user types [ctrl], [windows key], [alt], [space]... However, what was supposed to be a BIOS level interupt is caught by MS Windows, and blocks me from catching the keys when Windows's focus is on notepad or any other program.

Why those particular keys, and what does this have to do with a BIOS-level interrupt?

eschew obfuscation

Tedd

#3
December 01, 2007, 03:14:11 PM
Those keys do not generate normal keypress messages.
Luckily you don't need to do anything special - use GetAsyncKeyState or GetKeyState to check that each of the keys are down.
No snowflake in an avalanche feels responsible.

MicronXD

#4
December 02, 2007, 08:16:46 AM
Quote from: MichaelW on December 01, 2007, 12:06:16 PM
QuoteI'm trying to make a small app that will open it's GUI when the user types [ctrl], [windows key], [alt], [space]... However, what was supposed to be a BIOS level interupt is caught by MS Windows, and blocks me from catching the keys when Windows's focus is on notepad or any other program.

Why those particular keys, and what does this have to do with a BIOS-level interrupt?

Ur a mod? lol

MicronXD

#5
December 02, 2007, 08:19:55 AM
Quote from: Tedd on December 01, 2007, 03:14:11 PM
Those keys do not generate normal keypress messages.
Luckily you don't need to do anything special - use GetAsyncKeyState or GetKeyState to check that each of the keys are down.

Thx :D
Print
Go Up Pages1
User actions