it's all about each OS' API;
for Windows, u need to find the Win32 API which can read the hardware's
data out.
Go can call the API via syscall, or load the DLL in your app.
BR fino
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscr
https://developer.apple.com/library/content/documentation/ServicesDiscovery/Conceptual/GameControllerPG/Introduction/Introduction.html
https://developer.apple.com/documentation/gamecontroller
I have no idea why they don't include some Gamepad thing in the settings
panel.
On Tuesday, 27 March 20
Thanks for the pointers. I spent some time last night finding the gamepad
code in the Chromium sources, although I haven't had a chance to really
read it properly.
It makes sense that you'd read against some kind of OS-specific
abstraction, but I was curious what it was because I don't see any
Ah, just noticed the Mac part...
https://github.com/glfw/glfw/blob/master/src/cocoa_joystick.m
Also Chromium source for the Gamepad implementation:
https://cs.chromium.org/chromium/src/device/gamepad/?q=gamepad&sq=package:chromium&dr
Unfortunately I didn't notice a Go gamepad implementation for
Usually controllers don't speak directly to your application nor browser.
Usually there is a driver that the controller has, this talks with the
appropriate protocol to the device. The driver itself provides some common
HID api that the OS has specified.
The reading and writing the input is eff
