Wacky Keyboard Codes in keyconfig.plist...... AARRRRRGGGGHHH

For test results, bug reports, announcements of new builds etc.

Moderators: winston, another_commander, Getafix

User avatar
Micha
Commodore
Commodore
Posts: 815
Joined: Tue Sep 02, 2008 2:01 pm
Location: London, UK
Contact:

Re: Wacky Keyboard Codes in keyconfig.plist...... AARRRRRGGG

Post by Micha »

phrashee wrote:
Annoyed and done with it. It's sad that trying to solve some problem for the other users ends up in so much frustration.
I'm sorry you feel that way. I did attempt to work out what you were wanting and I'm sorry if I misunderstood or if my replies were unclear.

Based on your first couple of messages I went with the assumption that you pretty much knew what you were talking about (especially since you mentioned a coding background) and just had trouble working out where the special keycodes come from (which, without knowing more about the code, is hardly surprising as they are bespoke).

Since your only question seemd to be about the keycodes I told you what they are, and why Google didn't help. Furthermore, since you had already started digging into the code I figured you knew enough about it and just needed pointing in the right direction.

The questions you asked where we pointed you at the Wiki -are- in the Wiki: all the possible key commands which can be mapped in Oolite are there, and instructions on how to make your own keyconfig.plist. It's pointless repeating that here. In fact I spent some time yesterday (during my lunch hour) adding the 2 or 3 additional commands added in the last version of Oolite.

The bit which -isn't- in the Wiki are the non-ASCII key codes, which based on your first posting, I presumed you had more or less worked out. And for this information nobody pointed you at the Wiki but rather at the code which you had already found and seen.
Again, apologies if I assumed that you knew more about coding and that that was sufficient.

Anyway, here are the codes (again):

Code: Select all

enum GameViewKeys
{
gvFunctionKey1 = 241,
gvFunctionKey2,  // 242
gvFunctionKey3, // 243
gvFunctionKey4, // 244....
gvFunctionKey5,
gvFunctionKey6,
gvFunctionKey7,
gvFunctionKey8,
gvFunctionKey9,
gvFunctionKey10,
gvFunctionKey11,
gvArrowKeyRight,
gvArrowKeyLeft,
gvArrowKeyDown,
gvArrowKeyUp,
gvMouseLeftButton = 301,
gvMouseDoubleClick, // 302
gvHomeKey, // 303...
gvEndKey,
gvInsertKey,
gvDeleteKey,
gvPageUpKey,
gvPageDownKey,
gvNumberKey0 = 48,
gvNumberKey1, // 49
gvNumberKey2, // 50...
gvNumberKey3,
gvNumberKey4,
gvNumberKey5,
gvNumberKey7,
gvNumberKey8,
gvNumberKey9 //57
};
and they do increase linearly from the last explicitly stated constant, as you correctly surmised.
I'll add them to the Wiki page when I get some time..

I'll (continue) to do my best to explain, but please remember that nobody here is a paid support engineer, many people on the forum don't have english as their first language (myself included), and we're all just doing this in our spare time (of which there isn't much) and for fun.


Cheers,
- Micha.
The glass is twice as big as it needs to be.
Post Reply