Key combinations from wtype / ydotool are not registered about xournalpp HOT 5 CLOSED

If you are using software that captures your keystrokes, it may be recognized as one separate device. In my case this happened when I used xkeysnail. Open the Input Systems tab in Preferences and check if such a device appears in Input Devices. In my case it appeared as py-evdev-uinput (mouse), and I configured it as Mouse+Keyboard.

from xournalpp.

This should be fixed on master (via #5646).

from xournalpp.

I've just compiled the latest version but it has the same issue unfortunately.
I'm currently using wayland so xkeysnail is not an option for me. I also can't see any special input devices beeing detected when I use wtype.

If there's any other method to make the buttons work (Wacom Intuos S BT under Sway / Wayland) I'm interested to know about it. I know opentabletdriver and I'm able to make everything work with this driver, however my goal is to not depend on it because my device is already supported natively (by wacom kernel module / libinput) and opentabletdriver has no bluetooth support.

The only combinations so far that get picket up by xournal++ currently is Up and Down. Today I tried to work around the issue by installing the vi plugin (https://github.com/raw-bacon/vi-xournalpp), but I discovered that even single keys like 'd' don't get recognized by xournal++ (via wtype).

from xournalpp.

Can you get wtype to work in gtk-demo? (Make sure it's the gtk3 version of gtk-demo)

from xournalpp.

Nope, unfortunately it doesn't work there either, at least not with the current version in debian stable. I think I probably have to try a more recent version of ydotool. From what I see wtype looks somewhat abandoned currently in terms of development activity. I'm not sure if this is a general wayland problem because I once read it has issues with virtual input devices but I thought they are now mostly fixed. But anyway, I guess it looks like it's probably not primarily an issue with xournal++ then?

from xournalpp.