Comments on: List Desktop Shortcuts

By: Rob van Gelder

Rob van Gelder — Tue, 03 May 2005 05:16:00 +0000

From my assembler programming days…

I’ve memorised the bit equivilent for each nibble:
0 = 0000, 1 = 0001, 2 = 0010, 3 = 0011
4 = 0100, 5 = 0101, 6 = 0110, 7 = 0111
8 = 1000, 9 = 1001, A = 1010, B = 1011
C = 1100, D = 1101, E = 1110, F = 1111

So I can work out in my head which bits are set or not given a hexadecimal number.

Yes, I am a geek

By: Dick Kusleika

Dick Kusleika — Tue, 03 May 2005 03:18:00 +0000

Ding Ding Ding Ding. It makes perfect sense now. Integer = 16 bits = 2 bytes. High order = 256 and above, low order = 128 and below.

More dumb questions: Why do they say Shift=1 instead of Shift = 256 (if they would have said that I would have got it)? Why do you use hex in your comparison instead of (oLnk.Hotkey And 256)?

Thanks, Rob.

By: Rob van Gelder

Rob van Gelder — Tue, 03 May 2005 00:52:00 +0000

According to the MSDN article:
"The virtual key code is in the low-order byte, and the modifier flags are in the high-order byte"

Something like this applies:

IIf((oLnk.Hotkey And &H100) = 0, "", "Shift ") & _
IIf((oLnk.Hotkey And &H200) = 0, "", "Ctrl ") & _
IIf((oLnk.Hotkey And &H400) = 0, "", "Alt ") & _
Chr(oLnk.Hotkey And &HFF)