warpd VS xf86-input-wacom

I also enjoyed using https://github.com/rvaiya/warpd on my mac. But was hit with few bugs, where the pointer used to get stuck. Had to keep restarting. But still a nice program to ditch mouse.

for something similar that works with anything even beyond your browser there's warpd. I haven't used it I just know it exists. If you're into custom keyboards QMK can send mouse movements from keypresses too.

So I am trying to compile warpd, i followed and installed the dependencies, but when I make, it outputs wayland-client.h not found. Fair enough, I installed geckolinux TW Plasma, NVIDIA working fine, X11 session. I used "zypper se", it showed wayland is installed but nevermind; in the docs they have said that you can 'Set options' to only compile X11 binary. I want only that but I am just racking my brain where to insert 'DISABLE_WAYLAND' option. I know its a most basic and obvious setting but i come from arch where i fully relied on AUR for building so i zero compiling knowledge. I tried RTFM but idk what I have to find. I would be helpful if someone helps me here

Hey there! You should definitely check out warpd. It's a modal keyboard-driven pointer manipulation program that can help you control the pointer on your screen using just your keyboard.

I think you're maybe thinking of warpd? https://github.com/rvaiya/warpd

warpd avoided me spending a lot of time going from the keyboard to the mouse,for simple point and clicks. Honestly it is super useful.

https://github.com/rvaiya/warpd

Maybe you'd find warpd intersting.

I'd like to minimize my need for a mouse but there are some tasks which are just so much simpler with a cursor. I do have some mouse keys setup with Karabiner so that holding "k" and pressing esdf moves the cursor, but I've found this difficult to get used to. I have a few different keys to modify the speed, but it just feels way too convoluted and effortful to to control the cursor this way.

I've also tried warpd [1] but had some issues with it that turned me off to it.

Curious to know if anyone here has had success with something else

[1] https://github.com/rvaiya/warpd

I actually wrote this after seeing https://github.com/rvaiya/warpd on HackerNews and saw multiple people lament that they'd like to be able to use that for Windows. You should definitely check that out!

I tried the QT_XCB_TABLET_LEGACY_COORDINATES=1 fix on https://github.com/linuxwacom/xf86-input-wacom/wiki/Known-Issues#android-misdetect

What if you switch to x11 when using the tablet and log into wayland when you're done? Probably not ideal and you'll lose the touchpad gestures. their wiki has more info but might not be what you're looking for https://github.com/linuxwacom/xf86-input-wacom/wiki/Wayland

May be worth to take a look at https://github.com/linuxwacom/xf86-input-wacom/wiki/Known-Issues and in general the page. There seems to be quite a bit you can configure and calibrate by hand.

On most distros it should just work. However, there are a few hiccups in some distros / tablets. See this link: https://github.com/linuxwacom/xf86-input-wacom/wiki/Known-Issues

It doesn't look like a bug report was ever filed by the other reporter. Would you mind creating a bug report at https://github.com/linuxwacom/xf86-input-wacom/issues/ for us on the linuxwacom team to track? You should include the following information in your report:

Major issues ------------ Breeze Light color scheme not initially applied correctly - https://bugzilla.redhat.com/show_bug.cgi?id=1963709 xorg-x11-drv-wacom breaks touchscreen touch events for Qt apps - Upstream issue: https://github.com/linuxwacom/xf86-input-wacom/issues/178 - Maybe work around it in Fedora? https://pagure.io/fedora-kde/SIG/issue/77 - Workaround: run xsetwacom set `xsetwacom --list devices | grep TOUCH | cut -d " " -f 8` gesture off GTK apps produce horrible jarring beeps when run on KDE Plasma - Upstream issue: https://phabricator.kde.org/T14523 - Maybe work around it in Fedora? https://pagure.io/fedora-kde/SIG/issue/83 Installing KDE Connect should automatically create a relevant firewall allow-list for it - https://bugzilla.redhat.com/show_bug.cgi?id=1968002 Minor issues ------------ DNF packageKit plugin does not support DependsOn operation, so Discover can't show app dependencies - https://bugzilla.redhat.com/show_bug.cgi?id=1983315 org.freedesktop.accounts.change-own-user-data unnecessarily prompts for admin password, so various System Settings Users KCM operations are annoying for admins and unusable for regular users - https://bugzilla.redhat.com/show_bug.cgi?id=1988509 Feature requests/nice-to-haves ------------------------------ In Fedora, plasma-discover-flatpak-backend should add flathub repo during installation - https://bugzilla.redhat.com/show_bug.cgi?id=1524756 Package CryFS so that plasma-vaults can use it as a backend - https://bugzilla.redhat.com/show_bug.cgi?id=1963740 Install plasma-firewall by default - https://pagure.io/fedora-kde/SIG/issue/34

xorg-x11-drv-wacom breaks touchscreen touch events for Qt apps - Upstream issue: https://github.com/linuxwacom/xf86-input-wacom/issues/178 - Maybe work around it in Fedora? https://pagure.io/fedora-kde/SIG/issue/77 - Workaround: run xsetwacom set xsetwacom --list devices | grep TOUCH | cut -d " " -f 8 gesture off