VKcode always for upperccase?

[Annonyreeder]

$hook = DllStructCreate($tagKBDLLHOOKSTRUCT, $lParam)

        Local $flags = DllStructGetData($hook, "flags")
        Switch $flags
            Case $LLKHF_UP
                ConsoleWrite("vkCode - " & DllStructGetData($hook, "vkCode") & @TAB & "Char - " & Chr(DllStructGetData($hook, "vkCode")) & @CRLF)
        EndSwitch

Code works fine for the most part but VKcode always is uppccase ignoring the reality...
Example:
a = 65

b = 66

c = 67

etc...

Anyone had this issue before? Is this maybe deprecated or have a missed something?  I'm on latest windows 10 with a UK keyboard layout if that matters...

Edited November 25, 2019 by Annonyreeder

[BrewManNH]

Your question is unclear, what is being returned upper case only, or upper case when you have lower case in the struct? CHR 65 is "A", not "a".

[Annonyreeder]

Currently the VKcode will always come back as the uppercase version.
If i press 'a' (as opposed to 'A') the VKcode still comes back as 65.

Lowercase in struct but still showing '65' as if it was uppercase.
This is the same for all characters.

 

Edited November 25, 2019 by Annonyreeder

[TheXman]

1 hour ago, Annonyreeder said:

Anyone had this issue before? Is this maybe deprecated or have a missed something?

The confusion appears to be that you think Virtual Key Codes and characters are synonymous.  Virtual key codes represent the keys that are sent by the input device, not the characters that are generated.

Edited November 25, 2019 by TheXman

[Annonyreeder]

Right ok so that's normal?
The example in the documentation for '_WinAPI_SetWindowsHookEx' suggests otherwise so that is where  the confusion came from. Though searching online suggests you maybe right. I guess i'll have to look into keyboard events instead. Shame.

https://www.autoitscript.com/autoit3/docs/libfunctions/_WinAPI_SetWindowsHookEx.htm

If (($iKeycode > 64) And ($iKeycode < 91)) _ ; a - z
Or (($iKeycode > 96) And ($iKeycode < 123)) _ ; A - Z
Or (($iKeycode > 47) And ($iKeycode < 58)) Then ; 0 - 9

 

[Nine]

Well it is not that complicated to test for VK_SHIFT and VK_CAPITAL to decide whether the key is lower or upper.  Just add a couple of booleans.

[Annonyreeder]

That's too hacky for what I wanted to do tbh.
Though if anyone is interested I did come across this very nice UDF which solves all my problems.

 

[TheXman]

30 minutes ago, Annonyreeder said:

Right ok so that's normal?
The example in the documentation for '_WinAPI_SetWindowsHookEx' suggests otherwise so that is where  the confusion came from. Though searching online suggests you maybe right. I guess i'll have to look into keyboard events instead. Shame.

https://www.autoitscript.com/autoit3/docs/libfunctions/_WinAPI_SetWindowsHookEx.htm

If (($iKeycode > 64) And ($iKeycode < 91)) _ ; a - z
Or (($iKeycode > 96) And ($iKeycode < 123)) _ ; A - Z
Or (($iKeycode > 47) And ($iKeycode < 58)) Then ; 0 - 9

 

I agree.  That snippet, from the _WinAPI_SetWindowsHookEx example, is misleading and could easily cause confusion.