7 comments

[ 5.5 ms ] story [ 14.3 ms ] thread
I'm not quite sure why they opted for such a round about way of including bindings instead of using cargos "features" section.

I'm guessing it has to do with using local files to create the bindings.

This is very cool, and I'm excited to dig in and try this out for native Windows applications.

The Windows API is daunting, though. I've worked through their examples and reviewed the documentation on Github, but it's a bit overwhelming. If anyone knows of a good resource for learning more (for someone who has not practiced in creating native Windows apps), I would be grateful.

Hey,

I the win32 api looks harder than it is. Most of it is reading documentation.

I suggest the book "Programming Windows" by Charles Petzold.

If you know basic C, the win32 api is pretty well documented.

Any suggestions how to learn using WinRT for UIs (with Rust)?
Sorry, I haven't use the WinRT fir rust. I would suggest making a a simple window with a button in C and then try porting all the functions to the rust library.
Does this replace the winapi crate? I’ve been using that crate for things like IAudioClient3, but it seems to have fallen out of regular maintenance https://github.com/retep998/winapi-rs
It's meant to cover the entire Windows API, so that includes everything the winapi create covers. I've successfully ported over my projects that used winapi with few problems.