k-visscher/intellimouse-ctl

A cross-platform command line tool and library for Microsoft's IntelliMouse devices.

intellimouse-ctl's Issues

Error on MacOS: `OSError: open failed`

I'm having issues running this in MacOS 12.2.1.

$ intellimouse-ctl list
0. ProIntelliMouse @ "DevSrvsID:4295139340"
$ intellimouse-ctl get --dpi 0
Traceback (most recent call last):
  File "/usr/local/bin/intellimouse-ctl", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.9/site-packages/intellimouse_ctl/__init__.py", line 119, in main
    with _connected_devices()[namespace.index] as device:
  File "/usr/local/lib/python3.9/site-packages/intellimouse/intellimouse.py", line 33, in __enter__
    self._device.open_path(self._path)
  File "hid.pyx", line 125, in hid.device.open_path
OSError: open failed

Cannot run/build on arch linux

I could not figure out how to use this on arch linux.

First following the instructions from README.md, the dependecies failed:

INFO: pip is looking at multiple versions of fbs to determine which version is compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement sip<4.20,>=4.19.4 (from pyqt5) (from versions: 5.0.0, 5.0.1, 5.1.0, 5.1.1, 5.1.2, 5.2.0, 5.3.0, 5.4.0, 5.5.0, 6.0.0, 6.0.1, 6.0.2, 6.0.3, 6.1.0, 6.1.1, 6.2.0, 6.3.0, 6.3.1, 6.4.0)
ERROR: No matching distribution found for sip<4.20,>=4.19.4

Removing the version requirements from the requirements.txt got me to this:

The free version of fbs only supports Python 3.5 and 3.6.
Please obtain fbs Pro from https://build-system.fman.io/pro.

On arch the python is Python 3.9.9

And if I just tried to run python3 src/main/python/main.py, I got the error device not found. (With sudo I got the error but the controls were visible under it.)

Where are the pre-built binaries?

I am sorry -- a little bit lost here.
Where are the pre-built binaries?
Thanks!

Separate the logic for controlling the mice from the GUI application

• Make a PyPi package for writing/reading the mice.
• Let the GUI depend on it (and any other application that wishes to)

This should address the following use case: #1

Support the Classic IntelliMouse

I have a Classic Intellimouse at work I can test with, but due to covid I haven't been able to test your gist with it yet. Will do it as soon as I can!

If it works, it would be neat if this control panel also could support the classic mouse :)

Make the backend available as a cross-platform library

This is really cool. Thanks for making it!

I would love to support Microsoft Mice in Mac Mouse Fix. For that it would be awesome to have a cross-platform library that lets you talk to Microsoft Mice. This would also make it a lot easier to write great drivers for MS mice on linux.

I think a command line tool would also be fine.

Rewrite the HID logic using cython-hidapi

Since this pull request got accepted we can rewrite it entirely using hidapi.

Cannot run app without sudo in Big Sur (macOS 11.0.1)

Before I start: Great job, i love Intellimouse (best MS product ever) an am very happy that i found your repo.

In Big Sur (macOS 11.0.1) it seems, that up to now, Apple has problems with a mouse polling rate >125.
So i was looking for a solution. One way would have been to configure the mouse in windows 10.
But especially since i'm in homeoffice (we have currently a covid lockdown here in austria) i cannot plugin my mouse to a windows workstation.

So i tried your solution and i was able to build the App in Big Sur, but i can only run it in Terminal with sudo:
sudo ~/Desktop/microsoft-intellimouse-pro-control-panel.app/Contents/MacOS/microsoft-intellimouse-pro-control-panel
(Then i was able to set polling rate, led color, etc.)

Otherwise there is i assume a problem with the rights and the app tells only that something went wrong.

Make intellimouse.py not take over the usb interface on Linux

It would be neat if it was possible to use the mouse at the same time as you're setting it up so you can e.g. feel the different DPI settings.

I guess I should try to come up with a patch here myself, but I'll create the issue nevertheless.