The int key code values from Qt::Key_Space (0×20) until Qt::Key_AsciiTilde (0×7f) map directly to the respective ASCII codes of the characters. So it should be safe to do this:

Thanks, that worked…a bit. :-(

Seems that key() doesn’t handle shift key at all (not just the upper/lower cases), so I need to manually extinguish “!” and “1”, “{” and “[”, etc.

Yes. It handles the raw keys from the keyboard and does not interpret it into the (possible) character that is composed of the key and the modifiers. For that purpose the text() method exists.

But text() is not available when modifiers present. :-( Well, I guess I’ll just manually mapped all non-alphanumeric keys on my keyboard. But how about keyboard layouts? £ instead of $ above 4 on british keyboard, ¥ instead of \ on Japanese keyboards, etc. Is there a way for me to detect this on run-time?

Is there any way you could just use QKeySequence instead of trying to handle the raw events yourself?

I am building something similar to a terminal simulator that sends things like ctrl + ! to the server. The format the server takes (for the above example) is a CTRL, and then an ASCII ‘!’, so I need to get the result of the keyboard output to send (through a TCP socket).

That depends on the modifiers. What text do you expect for Ctrl-C?

For alphabets the cases don’t matter, so for ctrl + c both CTRL + ‘C’ and CTRL + ‘c’ are fine. I don’t participate in the server side programming, so I’m not sure what they intend to do with non-ASCII keys. (Most likely they don’t care — the system we are building is not for public use, and we use mostly US-layout keyboards. My plan now is to ignore the problem and leave it for the testing team to worry about. :-p)

Programming by delegation … good idea for the weekend approaching ;-P