Closed IgorKorobeynikov closed 2 months ago
Thanks for reporting!
The two lines really shouldn't be different, Vector2f.new(...)
does exactly what you do. I'm going to investigate this on my own pc and see if it happens here too, but it sounds to me like it's a bug outside my wrapper. It may be related with vector2f being a packed struct because I've heard packed struct have lots of bugs.
If you have any new info, keep me updated ^^
Thanks for reporting! The two lines really shouldn't be different,
Vector2f.new(...)
does exactly what you do. I'm going to investigate this on my own pc and see if it happens here too, but it sounds to me like it's a bug outside my wrapper. It may be related with vector2f being a packed struct because I've heard packed struct have lots of bugs. If you have any new info, keep me updated ^^
Thank you, I appreciate your work
@Guigui220D I've been digging into the zig and raylib-zig repositories, and I seem to be sure that this problem is related to this: zig issue 1481 zig issue 10560
Both issues were closed and the bug doesn't seem to happen anymore If it does let's reopen an issue
with this:
sprite.setPosition(.{ .x = 500, .y = 350 });
I get this: But with this:I get the expected result