Rust FFI: Microsoft Flight Simulator SDK Part 1 

1:08:50 If you're making a safe wrapper for c/c++ library bindings you should abstract away from using c types. I believe it'd be more idiomatic to pass in a regular String and convert it to what you need inside of the new method so the user doesn't have to think about using types that they aren't used to.

A few things I noticed: - 0 being equivalent to NULL is not a Windows thing, but a C++ thing. NULL was *required* to be defined as 0 (unlike C which *may* also define NULL as (void*)0) until C++11 which introduces nullptr, which has the advantage of disallowing silently interpreting 0 as a null pointer. Also helps in avoiding calling the wrong overload. - HRESULT can be non-zero but successful. Only negative HRESULT values indicate failure, which is why the C++ code used the SUCCEEDED macro. - For string constants you can use std::ffi::CStr::from_bytes_with_nul to avoid an allocation just to add a null byte (albeit requiring you to explicitly pass a \0-terminated byte-string)

that's literally the learning material I've been looking for ages, thanks so much Ryan! the pace of the video is just perfect :)

Thank you for this Ryan :) Hope you continue with these kinds of videos.

Love the "successful compilation"-cheers 😁 Great stream, looking forward to the next!

Fantastic! Thank you! Are you planning to do more MSFS tutorials?

I'm pretty sure that the Win32 Sleep() call waits in milliseconds, not seconds. That's why there was such a delay between you hitting the brake and the event triggering.

I like how you adjusted to using the term "allowlist" :)

Great stuff! I hope that you'll do a part 2 soon!

1:03:30 I like the using match blocks when there is a conditional return since it looks cleaner: match hr { 0 => Ok(Self { handle }), _ => Err(hr) }

Also, I vote for a part two of this. 👍

Great video. Thanks for share.

Good video!

The name pointer is dangling after SimConnect::new(). I haven't been able to find any documentation on the required lifetime of the pointer, so I can't say for sure, but this definitely smells of unsoundness.