kc3-lang/SDL/src/sensor/windows
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
e8c3ff56 | 2022-03-17 10:01:13 | Removed problematic call to ISensor_SetEventSink() Fixes https://github.com/libsdl-org/SDL/issues/5288 | |
|
120c76c8 | 2022-01-03 09:40:00 | Updated copyright for 2022 | |
|
3ba9276a | 2021-11-28 21:14:02 | Don't fail the sensor init if we couldn't create a sensor manager (i.e. we're running on Wine) Fixes https://github.com/libsdl-org/SDL/issues/5031 | |
 |
844d5e3e | 2021-02-21 11:54:50 | Fix memory leak in ConnectSensor 'name' is leaked in case of error. | |
 |
265a1cc9 | 2021-01-05 15:50:02 | use WIN_StringToUTF8W instead of WIN_StringToUTF8 where needed (#2) cf. bug #5435. - SDL_wasapi_win32.c (GetWasapiDeviceName): pwszVal is WCHAR* - windows/SDL_sysfilesystem.c (SDL_GetBasePath, SDL_GetPrefPath) - windows/SDL_sysurl.c (SDL_SYS_OpenURL): wurl is WCHAR* - SDL_windowssensor.c (ConnectSensor): bstr_name is WCHAR* - windows/SDL_systhread.c (SDL_SYS_SetupThread): strw is WCHAR* | |
|
9130f7c3 | 2021-01-02 10:25:38 | Updated copyright for 2021 | |
|
56622f9c | 2020-06-17 10:09:07 | Fixed bug 5126 - MinGW compile error SDL_windowssensor.c Martin Gerhardy SDL_windowssensor.c includes InitGuid.h - but it should be initguid.h | |
 |
a299fdd7 | 2020-05-21 03:52:48 | sensor: Fixed compiler warnings on mingw64. | |
|
b4e76b58 | 2020-05-20 17:32:23 | sensor: Fix overaggressive search/replace. :) | |
|
27c38eb2 | 2020-05-20 17:22:52 | sensor: Correct fix for redefinition of various symbols. | |
|
c9d358bc | 2020-05-20 16:59:35 | sensor: Fix build on various Windows compilers with various predefinitions. | |
|
68777406 | 2020-05-20 16:58:33 | windows: Fix calls to CoCreateInstance() so last parameter is a LPVOID *. | |
|
0f374b06 | 2020-04-22 15:42:32 | Fixed build on older Visual Studio, enable new features on newer Visual Studio | |
|
aba27928 | 2020-04-18 21:41:37 | Added a Windows Gaming Input joystick driver This driver supports the Razer Atrox Arcade Stick Some of the quirks of this driver, inherent in Windows Gaming Input: * There will never appear to be controllers connected at startup. You must support hot-plugging in order to see these controllers. * You can't read the state of the guide button * You can't get controller events in the background | |
|
e9c94ac0 | 2020-04-08 10:27:30 | Fixed Windows accelerometer data units | |
|
09f55263 | 2020-04-08 09:00:10 | Fixed memory leak and removed debug code from Windows sensor implementation | |
|
3180ba81 | 2020-04-08 08:34:27 | First pass at Windows sensor implementation |