Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WiimoteReal: Remove WiimoteScannerDarwin #10013

Merged
merged 1 commit into from Aug 13, 2021

Conversation

OatmealDome
Copy link
Member

Title.

I think this should be done for several reasons:

  • It pegs my CPU at 95% for scanning even when Dolphin is idle
  • WiimoteScannerHidapi works fine on macOS (in fact, in my testing, hidapi always connects a Wiimote first before the Darwin-specific code...)
  • Less macOS code to maintain

For several reasons:
- It pegs the CPU at 95% for scanning even when Dolphin is idle
- WiimoteScannerHidapi works fine on macOS
- Less macOS code to maintain
@Techjar
Copy link
Contributor

Techjar commented Aug 10, 2021

Is there maybe some systems/configurations which won't work with hidapi?

@OatmealDome
Copy link
Member Author

hidapi uses the standard macOS IOKit HID APIs which have been basically unchanged in a while, so I don't see a reason why it wouldn't work on some Macs. It should be compatible with at least macOS 10.9 Mavericks given when the version in Externals was last updated (Dolphin requires 10.12 Sierra minimum).

I think it should be compatible with all configurations.

@Techjar
Copy link
Contributor

Techjar commented Aug 10, 2021

Alright. I'm just trying to think of any reason why we were keeping the Darwin code around in the first place. Having 2 functionally similar scanners seems a tad silly.

@lioncash lioncash merged commit 891726e into dolphin-emu:master Aug 13, 2021
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants