- 04 Aug, 2022 29 commits
-
-
Cebtenzzre authored
-
Cebtenzzre authored
-
Cebtenzzre authored
-
Cebtenzzre authored
-
Cebtenzzre authored
-
Cebtenzzre authored
I've painstakingly analyzed the existing web of calls to set the force-feedback callback, and replaced it with a chain of functions to set a controller pointer in ForceFeedbackHandler. EvdevController implements functions to do force-feedback using the kernel drivers for the input device.
-
Cebtenzzre authored
-
Cebtenzzre authored
-
-
-
-
-
Accidentally also added a message queue in evdev.
-
-
-
-
This receiver is not Microsoft original, though "mimics" MS USB Vendor ID; still perfectly compatible.
-
-
btn2string returns "DPAD_UP" when passed XBOX_DPAD_UP and gives similar responses for the other directions (DPAD_LEFT, DPAD_RIGHT and DPAD_DOWN). However, string2btn didn't accept those as input, rendering the output of --help-button confusing.
-
There are similar Thrustmaster products in existence but I don't know whether they have exactly the same USB identifier or protocol. Although all the buttons, including the triggers, have a very digital feel, almost all of them also provide analog values. Sadly the Xbox 360 controller only has analog triggers so this is mostly wasted.
-
This corrects OPTION_CALIBRARIOTION -> OPTION_CALIBRATION (which I only noticed because I was looking for the implementation of the calibration option and was having trouble finding it because of the spelling).
-
This was triggering an exception, causing the daemon to exit prematurely.
-
After a USB transfer error, either retry or properly disconnect if the device is no longer found.
-
use `libusb_handle_events_timeout_completed()` instead of `libusb_handle_events()` should fix #144
-
-
Now that the destructor crash is fixed, it hangs instead. The crash has probably always masked this issue. I don't understand libusb much as it isn't well documented but it seems that by the time we check that all transfers have been cancelled, new ones have already been submitted. Setting m_is_disconnected to true beforehand to indicate we are destructing appears to remedy this.
-
-
parse() is indirectly called by the destructor, which is not allowed when it is pure virtual, causing a "pure virtual function called" crash. We don't care about parsing when the controller instance is about to be destroyed so define a dummy method in the base case.
-
- 31 May, 2022 1 commit
-
-
Grumbel authored
-
- 01 Mar, 2022 1 commit
-
-
Grumbel authored
-
- 05 Dec, 2019 1 commit
-
-
Grumbel authored
-
- 24 Nov, 2019 6 commits
- 06 Jun, 2018 1 commit
-
- 03 Mar, 2018 1 commit
-
-
Grumbel authored
Fixing typo sensitivty -> sensitivity
-