Alex a7be8a2655 Prefer UVec2 when working with texture dimensions (#11698) ... # Objective The physical width and height (pixels) of an image is always integers, but for `GpuImage` bevy currently stores them as `Vec2` (`f32`). Switching to `UVec2` makes this more consistent with the [underlying texture data](https://docs.rs/wgpu/latest/wgpu/struct.Extent3d.html). I'm not sure if this is worth the change in the surface level API. If not, feel free to close this PR. ## Solution - Replace uses of `Vec2` with `UVec2` when referring to texture dimensions. - Use integer types for the texture atlas dimensions and sections. [`Sprite::rect`](a81a2d1da3/crates/bevy_sprite/src/sprite.rs (L29)) remains unchanged, so manually specifying a sub-pixel region of an image is still possible. --- ## Changelog - `GpuImage` now stores its size as `UVec2` instead of `Vec2`. - Texture atlases store their size and sections as `UVec2` and `URect` respectively. - `UiImageSize` stores its size as `UVec2`. ## Migration Guide - Change floating point types (`Vec2`, `Rect`) to their respective unsigned integer versions (`UVec2`, `URect`) when using `GpuImage`, `TextureAtlasLayout`, `TextureAtlasBuilder`, `DynamicAtlasTextureBuilder` or `FontAtlas`.		2024-02-25 15:23:04 +00:00
..
macros	Bump Version after Release (#12020)	2024-02-21 20:58:59 +00:00
src	Prefer UVec2 when working with texture dimensions (#11698)	2024-02-25 15:23:04 +00:00
Cargo.toml	Check cfg during CI and fix feature typos (#12103)	2024-02-25 15:19:27 +00:00