search

AndyFilter / YeetMouse

A fork of a fork of the Linux mouse driver with acceleration. Now with GUI and some other improvements!
GNU General Public License v2.0
19 stars 1 forks source link

Add desktop item to Nix package #3

Open kitten opened 1 week ago

kitten commented 1 week ago

Just adding a small convenience wrapper to add a desktop item for the Yeetmouse GUI.

cc @74k1: I'm not sure whether this resolves some of the startup issues as well that you've had (assuming you can test the desktop item launcher)

This is based on some Nix scripts I've found in nixpkgs, but I'm very unsure of whether more is needed. Presumably, this might work differently with X11, but some packages seem to imply that polkit and hence pkexec should always be available when a desktop manager is installed 🤔

74k1 commented 1 week ago

Hi @kitten Thanks for all your great work in this project! I really appreciate it. I'd love to test it out - but I'm currently struggling with an issue here: https://github.com/AndyFilter/YeetMouse/pull/1#issuecomment-2409068741

Quickly mentioning @AndyFilter: perhaps it'd be nice to enable issues on this repository?

AndyFilter commented 1 week ago

Thanks for the tip @74k1, I've enabled issues for this repository.

As for the problem you're faced with, there's not much I can do, as I'm not using NixOS and it very much looks like a NixOS related issue. Though from my point of view it has nothing to do with the value of NUM_USAGES, as it should only affect complex (or oddly programmed) mice.

I don't know what mouse you're using, but you could check if the "faulty" mouse is even correctly bound to the LeetMouse driver (look into /sys/bus/usb/drivers/leetmouse and plug and out plug the mouse, to see if anything changes). This would eliminate a lot of possibilities, if it turns out that it's not being bound by the installation scripts or the udev rules, then it's worth checking if raising the NUM_USAGES value to something like 100 solves the issue.

No matter the outcome though, I will hopefully have some time in the near future to work on the GUI side of device binding, to allow users to manually chose devices they want to bind to the LeetMouse driver.

AndyFilter commented 1 week ago

I don't want to write about some vaguely related issues on this PR, but I also don't want to open an issue, for a problem that might already be solved, so without further ado. I've managed to push the code with the fix I mentioned last time quite swiftly, now comes the question. @74k1 did the last commit (https://github.com/AndyFilter/YeetMouse/commit/489bf1eaf5428b6b802cd8151e00acd4ed41e26a) allowed you to fix the issue and bind the unresponsive mouse? There should be a tab selection on the top of the program now, after clicking on the "Devices", you should be greeted by a menu allowing you to bind selected devices to the LeetMouse driver (and back to usbhid).

If this didn't solve the problem please open an issue, so we can work on it further there. (Or if I configured something poorly, and you can't open issues, please inform me about it)

If this did solve your issue, 👍 I'm happy that we've managed to fix the issue that was such a burden on some LeetMouse users since it's creation