Description
Panics when spawning a Component that utilizes an .aseprite file where a sprite's Canvas was resized (under certain conditions).
Sample Backtrace
bevy_aseprite_reader-0.1.1/src/computed.rs:765:26:
Image index (1, 9) out of bounds (11, 9)
Steps to reproduce:
- in examples folder, open
crow.aseprite
- Enter canvas resize mode,
Sprite (C) -> Canvas Size...
- Draw a bounding box starting from the top left, leave default settings, confirm, save
- run example
Should see similar panic as above
Discussion
If you select
-[X] Trim content outside the canvas
the panic will not occur and behave as one would expect.
I imagine the ImageCel's untrimmed bounds are still parsed and present when the above option is not selected. Currently getting familiar with the codebase.
Is there any scenario where we are still interested in using a pixel that is out-of-bounds of the canvas?
Description
Panics when spawning a
Componentthat utilizes an.asepritefile where a sprite's Canvas was resized (under certain conditions).Sample Backtrace
Steps to reproduce:
crow.asepriteSprite (C) -> Canvas Size...Should see similar panic as above
Discussion
If you select
the panic will not occur and behave as one would expect.
I imagine the ImageCel's untrimmed bounds are still parsed and present when the above option is not selected. Currently getting familiar with the codebase.
Is there any scenario where we are still interested in using a pixel that is out-of-bounds of the canvas?