Janek Bevendorff

Cross-platform global shortcuts are surprisingly hard to implement. If you ask me, I would probably go for the second option as it looks cleaner to me. Unfortunately, Qt itself doesn't...

Thinking about it more: I would definitely move the three different registerGlobalShortcut() and platformEventFilter() implementations to a separate class that is used by both autotype as well as any other...

Can't we just load the plugin once and then use it for both?

I thin if we implement it, we should to it in the most extensible way we can. I would therefore maybe split the plugin and make a generic GlobalKeyboardActions interface...

I know. And it's a lot of work for just a simple feature. But the full autotype code is already super complex and adding more complexity in the form of...

If you want to add this feature now and quickly, do it the way you suggested. But in the long term, I'm afraid we have to do the refactoring. I've...

That looks cool, but it's missing the reverse direction, i.e., sending keystrokes. But maybe we can use it only for the hotkey part and remove that from the current autotype...

Umm, QGlobalShortcut has one major downside: the Mac implementation: ``` #include "qglobalshortcut.h" #include quint32 QGlobalShortcut::toNativeKeycode(Qt::Key k) { // TODO } quint32 QGlobalShortcut::toNativeModifiers(Qt::KeyboardModifiers m) { // TODO } void QGlobalShortcut::registerKey(quint32 k,...

That might actually also be a way for Wayland users to use autotype. Right now there is no solution for it. We'll have a look at it. 

Close your browser and try again.