sdl12-compat VS hidapi

I'm just glad so many of the SDL 1.2.x-era games dynamically linked SDL so I can use sdl12-compat to stick them on top of SDL 2.x's non-modesetting fullscreening and PulseAudio support.

Thankfully, most people don't statically link SDL 1.2, so it's possible to use sdl12compat to rebase them on top of SDL 2.x's non-modesetting fullscreening support, among other things.

There have been some efforts to keep them working: http://www.improbability.net/loki/ https://github.com/libsdl-org/sdl12-compat/

I've been determined to get the only system not on the device working in some way. The biggest issue to the Apple II systems not being present is that all the emulators are not written in SDL2 and the only Apple II emulator written in SDL2 (shamusworld) is far from perfect. So I tried my hand at something: What if I could wrap SDL1.2 to SDL2 against linapple? My brother showed me on github sdl12-compat https://github.com/libsdl-org/sdl12-compat. Amazingly enough, we have results. Now it's not going to be as functional this way like having RetroArch to configure things, but I have over twenty Apple II games pre-configured with controls thus far.

You need this compatibility library and you can drop it into the "lib" folder in the game files.

Here's the only useful link from the article: https://github.com/libsdl-org/sdl12-compat/releases/tag/release-1.2.52

It looks like the multiple monitor issue was known and theoretically fixed? https://github.com/libsdl-org/sdl12-compat/issues/38

Really old Linux games based on SDL1 can also work on Wayland by using the SDL1 on SDL2 wrapper in combination with a recent SDL2 build (I've been successful with Psychonauts this way, and it even solved some weird windowing problems with the game)

On the computer, write a program (the "host" or "server") that talks over the raw HID protocol. It is open ended how you do this, but IME both the Python pyhidapi and C hidapi were simple enough to get something started. The trickiest part might be getting the program to run with the permissions to talk the raw HID protocol (at least on Linux, there was some udev rule to set up). Read the documentation for these libraries for details about how to get set up.

now I'm trying to figure out what to do with the next step for building my own host. Am I supposed to put this test file in my qmk code? or run it on my computer as it's own separate program? https://github.com/libusb/hidapi/blob/master/hidtest/test.c

HIDAPI

I did star https://github.com/libusb/hidapi too, as well as this GitHub.

I used ffigen to get the bindings from hidapi.h and cleaned up quite some of the resulting output to make it Dart compatible. Quite some typedef and some minor stuff.

I figured out the problem with JoyconLib! The hidapi.dll file was broken so I replaced it with a new file from https://github.com/libusb/hidapi/releases and not it's working.

https://github.com/libusb/hidapi#prerequisites

Install the HID API, instructions here: https://github.com/libusb/hidapi

Inspired by https://askubuntu.com/questions/699138/logitech-k380-bluetooth-keyboard-make-function-keys-default and https://github.com/libusb/hidapi, it's almost re-implementation of hidapi actually, with dart:ffi calling the syscall directly.