You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting frames from a grid shows (at least for me) unexpected behavior when using ranges for both the x- and y-coordinates.
Expected: Get frames in order (a,q), (a+1,q), ... (b,q), (b,q+1) ... (b,r). Result: Frames in order (a,q), (a,q+1), ... (a,r), (a+1,q) ... (b,r). Possible Fix: Swap anim8.lua:78 with anim8.lua:79.
Example:
Consider this animation from opengameart.org: https://i.imgur.com/xFHuX.jpg
Frames are laid out as following:
grid('1-4,1-8') returns the frames 01,05,...,29,02,06,...30,03, etc. In order to get the correct frame ordering you have to specify the frames as grid('1-4,1', '1-4,2', '1-4,3', ..., '1-4,8').
It would be super cool if we could specify the preference of x and y, but I have no idea how the API would look like. ;)
The text was updated successfully, but these errors were encountered:
You're right, it's more intuitive to do the parsing "by rows". I don't think multi-dimensional animations are frequent enough to need a special case to differentiate this, so I'll just make it the default. If someone needs to parse "by columns", they will have to enter several parameters or rearrange their frames. Thanks for reporting this!
Getting frames from a grid shows (at least for me) unexpected behavior when using ranges for both the x- and y-coordinates.
Expected: Get frames in order
(a,q)
,(a+1,q)
, ...(b,q)
,(b,q+1)
...(b,r)
.Result: Frames in order
(a,q)
,(a,q+1)
, ...(a,r)
,(a+1,q)
...(b,r)
.Possible Fix: Swap anim8.lua:78 with anim8.lua:79.
Example:
Consider this animation from opengameart.org: https://i.imgur.com/xFHuX.jpg
Frames are laid out as following:
grid('1-4,1-8')
returns the frames01,05,...,29,02,06,...30,03
, etc. In order to get the correct frame ordering you have to specify the frames asgrid('1-4,1', '1-4,2', '1-4,3', ..., '1-4,8')
.It would be super cool if we could specify the preference of x and y, but I have no idea how the API would look like. ;)
The text was updated successfully, but these errors were encountered: