GlovePIE VS winsafe

I tried to use that program years ago, wasn't really satisfied. I believe there's a program that will let you use the keyboard as a... keyboard, I guess. https://github.com/Ravbug/GlovePIE

In theory you could use GlovePIE to map one of the keyboards to buttons in a virtual joystick.

I use GlovePIE to get around most of those. It's annoying that I have to set that up in the first place, but it works well.

The more boring way is install GlovePIE (see https://github.com/Ravbug/GlovePIE for an preservation archive site as the original site has fallen into disrepair) & use an IR sensor bar (like the original Wii sensor bar, which is just a set of 2 IR transmitters that the Wii used as a fixed reference point) to use it as an HID, like a mouse.

https://github.com/Ravbug/GlovePIE i use a software called glovepie to interpret MIDI inputs as keyboard presses. with this software you can use any MIDI device to emulate keyboards, mice, controllers, or whatever you want. here is my script that i created to use my piano as input for Lunatic Rave 2 and similar rhythm games as an example. There is also a built in GUI based key mapper which is helpful to set up MIDI devices (just press a button on the device and then the button you want to emulate).

Nice. The language looks really nice! I started out with GlovePIE (site went down about 1-2 years ago) (image). It was more a hotkey scripting/assigning language, allowing multiple types of syntax (bash or c like). I used it to map my Wii Remote to the keyboard and initially played some games using the classic controller mapped to mouse and keyboard.

You could try using Freepie or Glovepie this is how I bind my wii controllers to PC games.

Check out GlovePie.

You can use GlovePie on windows to have it output MIDI. I have been using it for years now. If you want the script I run for it feel free to DM me.

Just cleaning it to connect it to my PC using Glovepie: https://github.com/Ravbug/GlovePIE/releases/

I know all that shit because I'm the author of Rust's WinSafe library, which is a safer Rust layer over native Win32, so I had to deal with a lot of shit like this.

[dependencies] winsafe = { git = "https://github.com/rodrigocfd/winsafe", features = ["kernel"] }

Externally, you can write a lot of native Windows stuff in Rust already. Personally, I'm having a lot of fun with WinSafe.

If you had such problems (which I also had in the past), I'm really interested in you opinion about WinSafe, and if it could help you solving them.

If you're after a native Windows application, WinSafe may suit your needs.

As the author of WinSafe, I can say it's tedious sometimes, but it's often very challenging, because you have to translate crazy unsafe behaviors into Rust's ownership model. It's surely hard, but also very rewarding at the end.

As the author of the WinSafe lib, I wholeheartedly agree.

I don't know how rare this is (or how rare it should be), but this issue warned me about this potential problem, and I had to make a huge refactoring to treat the possibility. I had to rethink many aspects of all handle implementations. It was hard work, but in the end it was worth it.

WinSafe says hello.

WinSafe, for example (which attemps to be a safe layer over the Windows API), provides lots of RAII automations. A fine example is the BeginPaint function: