Info
This post is auto-generated from RSS feed The Rust Programming Language Forum - Latest topics. Source: Need help wrangling raylib
I've been trying to use the raylib crate, but I've been butting up against a pretty nasty issue: RaylibHandle::window_should_close()
simply refuses to return true for some reason. I can circumvent it for the escape key myself, but the close button on the window is unresponsive and I don't know what to do. I suspect it might have something to do with me accidentally compiling a dev build of raylib instead of 5.5 and cargo... I don't know, "capturing" it? What I do know is that I'm seeing INFO: Initializing raylib 5.6-dev
in the console when running my program, and compiling the correct version and rebuilding doesn't seem to fix it.
1 post - 1 participant
🏷️ Rust_feed