how to enter the same key used as a hotkey?

[Belini]

If you use _WinAPI_GetAsyncKeyState or use _IsPressed can enter the key in Notepad longer use hotkey can not enter the same key is to do this?

#include <Misc.au3>
#include <WinAPI.au3>
Const $MASCARA = 0x8000
Const $key_1 = 0x31; "1"
Const $key_2 = "32"; "2"
Const $key_3 = "3" ; "3"
Local $hDLL = DllOpen("user32.dll")
HotKeySet($key_3, "key_3")
Run("Notepad.exe")
While 1
$a_key_1 = _WinAPI_GetAsyncKeyState($key_1)
If BitAND($a_key_1, $MASCARA) Then Send("{1 10}")
If _IsPressed($key_2, $hDLL) Then Send("{2 10}")
Sleep(1)
WEnd
Func key_3()
Send("{3 10}")
EndFunc   ;==>key_3

[BrewManNH]

Hotkeys are usually set to use keys from the keyboard that you won't be using in the program you're interacting with. That's why you're rarely going to see a SHIFT+<some letter or number key> because you are expected to be using them in normal use. Use a different set of keys or you're just going to have to program around it by unsetting the hotkey when you enter the function, then resetting it as you return from from it.

[Belini]

So hotkey is only seen by the script to perform a function is no more seen by the OS

[BrewManNH]

Yes, a hotkey is system wide, if you map a hotkey for your script it's going to be sent to your script and not to any other window. If you want it to only go to your script, and only when the script's GUI is active, you'll need to use an accelerator key instead using GUISetAccelerator.

[Belini]

@ BrewManNH esclarescimentos thank you for, so even if someone has bad intentions can not use hotkeys to make keylogger, that is correct?

[Melba23]

Belini,

even if someone has bad intentions can not use hotkeys to make keylogger, that is correct?

You are not correct - a crude keylogger can very well be made using HotKeys.

Any code which looks to identify which key has been pressed from more than a very small selection is in breach of the rules - as I explained at length here. So a script with a HotKey for practically every key on the keyboard is most definitely NOT permitted.

Is that quite clear?

M23

[elektron]

I've wanted to do this a couple of times, actually, in AutoIt, but this was at the time that I was more comfortable with AutoHotKey than I was with AutoIt, so I ended up writing the solution in AutoHotKey and wrote it in AutoIt at a later time. There's a design pattern that you can use to actually intercept the hotkey, and still let the keypress go through.

Here's how it works:

The hotkey gets pressed, and so then the function associated with that hotkey gets called, so then what you do is you send that keypress back to the active window, from within the script.

As a general rule though, you don't want to have to do that. If you're writing a hotkey for your program that triggers some action or another, you want that hotkey to be a unique one.

-- Alex

[Belini]

@ Melba23 I have never had the intention of violating the forum rules only try to understand how to script using hotkey could be used to keyloog? The keystroke is only seen by the script and elsewhere over the keystroke is not seen then as a keylogger would be if only the script sees the key?

[Melba23]

Belini,

If you code a script which watches the keyboard and reacts when the keys are pressed, it does not take much effort to add a few lines of code to store these keystrokes somewhere and then send/collect them later. So you do not need to actually write a keylogger to fall foul of the Forum rules. That is why I say in the announcement to which I linked:

if you post any code which checks for the best part of the keyboard...

...do not post code which flouts the spirit, if not the exact letter, of the rules

The code you posted watched the entire keyboard so that it could light up the keys on the "virtual keyboard" GUI. Can you really not see how that could be very easily transformed into a full-blown keylogger?

Your intention is not important - it was the mere fact that you posted code which watched the keyboard that got you moderated. As Valik has said on many occasions, people need to think a little wider than just the immediate use of the code they post - the rules are there to prevent script kiddies getting a free ride. If I can use an awful analogy, giving them a free ticket is just as bad.

Does that make sense now?

M23

[Belini]

I agree with you that the script monitors the entire keyboard but to be used as a keylogger would have to be redone and all this does not use anything here, or need to use _WinAPI_GetAsyncKeyState _IsPressed and need to use this loop, case, if ... and none of these commands is the script I posted, most still consider that I posted the script can be adapted to be a keylogger I will not discuss it and give it closed then.

[Melba23]

Belini,

I agree with you that the script monitors the entire keyboard [...] the script can be adapted to be a keylogger

Exactly - so please do not post anything like it again.

M23

[Belini]

@ Melba23 consider you a great moderator and even not thinking like you give this matter closed and will not post code that can be interpreted as a keylogger, sorry for making you waste time on this subject.

[Melba23]

Belini,

Thanks.

M23