nokhwa VS windows-rs

Based on nokhwa rust crate.

It looks like the issue is with nokhwa. There are three open issues that reference the error: 72, 94 and 100. It looks like someone had luck switching from NV12 to YUYV after opening the stream but then I think you might end up with issue 90 where everything is pink so hyperbacked will infinitely loop waiting for an image since it can't actually read anything. The YUYV issue might have been fixed but the crate has been failing to build since the last release. That rules out setting the dependency to use the git repository. I think you just need to wait for a new release of nokhwa that fixes the issues but I don't know when that will be.

It is pretty painful and requires so much unsafe but I think the "not needing to deal with bindgen" and the Rust exclusive features make it worth it. If you need an example check out https://github.com/l1npengtul/nokhwa/tree/0.9.2/nokhwa-bindings-windows

I'd say Rust does have that big ticket ecosystem push. Microsoft has been embracing Rust lately, with things like official Windows bindings [1].

The bigger problem is just inertia: large game engines are enormous.

[1]: https://github.com/microsoft/windows-rs

It's a shame that, unlike with Win32, using WinUI places pretty harsh restrictions on which programming languages and environments you can use. Only C# and C++ are supported, the latter only with Microsoft compilers. For everything else, including Rust[1], Python and MinGW C/C++, there is no answer for OP's question, and the effect of this on the visual consistency of the Windows desktop is obvious - there is none. Every third-party app uses a different toolkit with a different look and feel, because the library providing the standard look and feel simply isn't available to the majority of developers.

[1]: https://github.com/microsoft/windows-rs/pull/1836

[0] https://github.com/microsoft/windows-rs

On Windows you'd need to call the LoadLibraryEx method. You'd also need a crate to call Win32 functions, I suggest windows-rs.

windows-rs, Microsoft's crate wrapping the Windows API, already includes the WDK, the special sdk for creating kernel code.

On windows, I'll probably use https://github.com/gabdube/native-windows-gui or https://github.com/microsoft/windows-rs both of them seem pretty solid.

*nod* It's an official Microsoft thing generated from official Microsoft API definition files. (The repo is at microsoft/windows-rs on GitHub.)

Microsoft offers official "bindings" to Win32 APIs through win32metadata. However, until recently, it did not include metadata for kernel-level functions or WDK. In early 2021, an issue was raised through windows-rs regarding this limitation, but progress was slow until now. Microsoft has finally released official metadata for WDK, which can be found on the wdkmetadata repository. The latest comment on the issue thread can be found here:

Is something wrong with https://github.com/deviceplug/btleplug or you haven't found it? You could also use bindings to platform libraries like https://github.com/microsoft/windows-rs and https://github.com/rust-mobile/ndk if btleplug doesn't have something fundamental to you.