MayeulC / MayeulC/Saitek

Various improvements

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
31
Forks
10
PR merge metrics
No merged PRs in 30d

Description

This issue is here to provide various ideas of improvements that can be done. Of course, feel free to discuss each of the items.

  • Make a new object "capabilities", listing the DPI, and various capabilities like battery level reporting and such, so that the interface adjusts accordingly.
  • Add support for multiple mice. Yes, the use case is not frequent, but this may be handy. With a device selector.
  • Add some sort of "profile" load/save option
  • Add an option to load different profiles based on the current mouse mode. Of course, this would need the program to always be running, which brings us to the next item...
  • Make a system tray icon, which will perform user-defined tasks, maybe even a button remapping functionality. I don't know if this approach to button-remapping is wayland-proof, though.
  • If the tray indicator is implemented, I also reverse-engineered quite some time ago (before the mouse, actually) the protocol required to speak to the Cybork V.7 keyboard's volume indicator. We could also make the program take care of updating it.
  • add a command-line interface. Would especially be handy since not everyone wants pyQt5 on their machine. It looks like @np has started something like that already. Part of this is tracked in #13

Also :

  • Investigate the possibility of contributing to Libratbag
  • Fix the kernel module to enable the mode button auto-release tweak on more devices
  • Add battery level reporting to the kernel module. I got stuck on this : http://codepad.org/GWZPwKyX (fixed the issue -wrong read size iirc- , but didn't write the module)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This issue bundles multiple independent features, names no files or tests, and notes that CLI work is partly tracked in #13. Start by reviewing the existing Python/pyQt5 application and #13, then split the remaining ideas into separate issues. Each follow-up should name its entry points and tests and define a specific completed behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python
Domain
cli, desktop, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.