forestia/bevy

Fork 0

Commit Graph

Author	SHA1	Message	Date
Lege19	3978ba9783	Allowed creating uninitialized images (for use as storage textures) (#17760 ) # Objective https://github.com/bevyengine/bevy/issues/17746 ## Solution - Change `Image.data` from being a `Vec<u8>` to a `Option<Vec<u8>>` - Added functions to help with creating images ## Testing - Did you test these changes? If so, how? All current tests pass Tested a variety of existing examples to make sure they don't crash (they don't) - If relevant, what platforms did you test these changes on, and are there any important ones you can't test? Linux x86 64-bit NixOS --- ## Migration Guide Code that directly access `Image` data will now need to use unwrap or handle the case where no data is provided. Behaviour of new_fill slightly changed, but not in a way that is likely to affect anything. It no longer panics and will fill the whole texture instead of leaving black pixels if the data provided is not a nice factor of the size of the image. --------- Co-authored-by: IceSentry <IceSentry@users.noreply.github.com>	2025-02-10 22:22:07 +00:00
atlv	d4883a9b5f	switch bevy_image to use wgpu-types wherever possible instead of wgpu (#16620 ) # Objective - dont depend on wgpu if we dont have to ## Solution - works towards this, but doesnt fully accomplish it. the remaining types stopping us from doing this need to be moved upstream, i will PR this ## Testing - 3d_scene runs --------- Co-authored-by: François Mockers <francois.mockers@vleue.com>	2024-12-03 11:46:10 +00:00
vero	8b0388c74a	Split off bevy_image from bevy_render (#15650 ) # Objective - bevy_render is gargantuan ## Solution - Split off bevy_image ## Testing - Ran some examples	2024-10-04 20:16:47 +00:00

Author

SHA1

Message

Date

Lege19

3978ba9783

Allowed creating uninitialized images (for use as storage textures) (#17760 )

# Objective
https://github.com/bevyengine/bevy/issues/17746
## Solution
- Change `Image.data` from being a `Vec<u8>` to a `Option<Vec<u8>>`
- Added functions to help with creating images
## Testing

- Did you test these changes? If so, how?
All current tests pass
Tested a variety of existing examples to make sure they don't crash
(they don't)
- If relevant, what platforms did you test these changes on, and are
there any important ones you can't test?
Linux x86 64-bit NixOS 
---
## Migration Guide
Code that directly access `Image` data will now need to use unwrap or
handle the case where no data is provided.
Behaviour of new_fill slightly changed, but not in a way that is likely
to affect anything. It no longer panics and will fill the whole texture
instead of leaving black pixels if the data provided is not a nice
factor of the size of the image.

---------

Co-authored-by: IceSentry <IceSentry@users.noreply.github.com>

2025-02-10 22:22:07 +00:00

atlv

d4883a9b5f

switch bevy_image to use wgpu-types wherever possible instead of wgpu (#16620 )

# Objective

- dont depend on wgpu if we dont have to

## Solution

- works towards this, but doesnt fully accomplish it. the remaining
types stopping us from doing this need to be moved upstream, i will PR
this

## Testing

- 3d_scene runs

---------

Co-authored-by: François Mockers <francois.mockers@vleue.com>

2024-12-03 11:46:10 +00:00

vero

8b0388c74a

Split off bevy_image from bevy_render (#15650 )

# Objective

- bevy_render is gargantuan

## Solution

- Split off bevy_image

## Testing

- Ran some examples

2024-10-04 20:16:47 +00:00

3 Commits