bevy_egui VS winsafe

I've heard that bevy_egui is good.

fwiw, I've had a blast using https://github.com/mvlabat/bevy_egui - you might find it easier as well.

Hi! Can't help but post a link to my plugin here: https://github.com/mvlabat/bevy_egui

Afaik, there are no plans to upstream Egui integration to Bevy, but if anyone needs an immediate mode UI, this plugin does the job (and it already supports Bevy 0.9).

It's much more mature than our UI solution (which is bevy_egui exists and is wildly popular). And for things like calculators and todo lists, there's no complex internal logic where you really want the tools that Bevy provides.

Oh, forgot to mention, egui is used for most of the gui features via bevy_egui, it's pretty nice, very easy to use (I've been using other immediate gui before).

For a GUI, you might consider egui which has an integration for bevy.

Bevy engine has also an editor UI plan like godot,but it's just the beginning. There is a Egui integration(bevy_egui) for the Bevy game engine which you can try.

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: