forum-msg-id-135109-edit

Original date:2020-10-13 00:26:33 Edited by: ghaberek Subject: Re: TAB KEY

achury said...

Is this a bug or a feature? Depends on the compiler used to build the interpreter?

If you take a look at the getKBcode() which is what does get_key() internally on Windows, you'll see at line 659 that it checks for the tab key (EuChar == 9) and then passes it through a big int[] array named VK_to_EuKBCode which then converts it to 0xF8080 (1015936), the value you're seeing. Apparently this is

So... why?

Well, it looks like Derek added all that on 12 Nov 2011 in commit 1e10f0d with the comment:

Windows keyboard now uses native API and also fixes keycode clashes with unicode chars 

And... I'm still not sure why. I mean, I get using the Windows API to read keyboard characters and avoiding Unicode problems, but the Unicode value for Tab is still 9.

achury said...

Just for that detail, the compatibility become broken.

This might just be a bug. I wonder if Derek's around to chime in on this.

-Greg

Not Categorized, Please Help

Search



Quick Links

User menu

Not signed in.

Misc Menu