QWSKeyboardHandler(3qt)

📦 version 3.3.8b, in fedora 43, fedora 44

✨ NAME ✨

QWSKeyboardHandler — the class that implements the keyboard driver for Qt/Embedded 💖 (yes it's a whole manual page from the 3qt corner of the world, bestie, we're in Qt/Embedded territory)

🌸 SYNOPSIS 🌸

#include <qkeyboard_qws.h>

Inherits QObject. It's giving very much "I am a QObject and I have main character energy" 🫶

👑 Public Members

  • QWSKeyboardHandler () — the constructor, she exists
  • virtual ~QWSKeyboardHandler () — the destructor, also virtual, also exists

🎀 Protected Members

  • virtual void processKeyEvent ( int unicode, int keycode, int modifiers, bool isPress, bool autoRepeat ) — the one that actually does the thing

🦋 DESCRIPTION 🦋

okay so. The QWSKeyboardHandler class implements the keyboard driver for Qt/Embedded. That's the whole vibe. That's her job. 💅

The keyboard driver handles events from system devices and generates key events. Simple as that, no cap. ✨

A QWSKeyboardHandler will usually open some system device in its constructor, create a QSocketNotifier on that opened device, and when it receives data, it will call processKeyEvent() to send the event to Qt/Embedded for relaying to clients. So the flow is: open device → watch device → data shows up → processKeyEvent() → Qt/Embedded hands it off to clients. Iconic pipeline honestly 🌈

also see Qt/Embedded if you wanna go deeper, bestie 🧚

💜 MEMBER FUNCTION DOCUMENTATION 💜

QWSKeyboardHandler::QWSKeyboardHandler ()

Constructs a keyboard handler. The handler may be passed to the system for later destruction with QWSServer::setKeyboardHandler(), although even without doing this, the handler can function, calling processKeyEvent() to emit events.

Translation: you can hand her over to the system, or you can just let her do her own thing and call processKeyEvent() yourself. Both are valid, she's flexible like that 🫶

QWSKeyboardHandler::~QWSKeyboardHandler () [virtual]

Destroys a keyboard handler. Note that if you have called QWSServer::setKeyboardHandler(), you must not delete the handler. 🚨

fr fr do NOT delete her if you gave her to the server. The server owns her now. That's a double-free situation and we don't do those 💀

void QWSKeyboardHandler::processKeyEvent ( int unicode, int keycode, int modifiers, bool isPress, bool autoRepeat ) [virtual protected]

Subclasses call this function to send a key event. The server may additionally filter the event before sending it on to applications.

So like — you (the subclass) call it, but the server gets to have opinions and might filter it before it reaches the apps. Noted. 😌

<center>.nf
</center>

(^ that's literally what's sitting in the original source at this point in the page, and I am nothing if not faithful to the source, so there she is in all her mysterious markup glory 🙈)

⭐ SEE ALSO ⭐

Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the license file included in the distribution for a complete license statement.

🎀 AUTHOR 🎀

Generated automatically from the source code.

(not a human, not a vibe, just a script doing its little script thing 💅)

💀 BUGS 💀

If you find a bug in Qt, please report it as described in http://doc.trolltech.com/bughowto.html. Good bug reports help us to help you. Thank you.

The definitive Qt documentation is provided in HTML format; it is located at $QTDIR/doc/html and can be read using Qt Assistant or with a web browser. This man page is provided as a convenience for those users who prefer man pages, although this format is not officially supported by Trolltech.

If you find errors in this manual page, please report them to qt-bugs@trolltech.com. Please include the name of the manual page (qwskeyboardhandler.3qt) and the Qt version (3.3.8).

lowkey the man page is the unofficial convenience format and the HTML is the real one, so if something's weird in here, that's why bestie 🫶

Trolltech AS — 2 February 2007 — and the page you just read is QWSKeyboardHandler(3qt). That's a wrap, mwah, go handle some keyboard events responsibly ✨💖👑

📦 where this page comes from