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
We could provide a "render order" or "z-index" field per cel, where lower values mean to render the layer first, and higher values render the layer overlapping the lower ones (just exactly like CSS z-index).
This field could be added in the Cel Properties dialog:
The text was updated successfully, but these errors were encountered:
dacap
changed the title
change layer ordering in a specific frame // we could provide a "render order" or "z-index" field per cel, where lower values mean to render the layer first, and higher values render the layer overlapping the lower ones (just exactly like CSS z-index)
Change layer ordering in a specific frame
Mar 29, 2023
* Now a Cel has a z-index property to change the order of layers per frame
* A new doc::RenderPlan class can calculate the order of cels to be rendered
* z-index is saved as a int16_t in the .aseprite files
* This new field can be set/get from Lua with Cel.zIndex
dacap
added a commit
to aseprite/strings
that referenced
this issue
Jan 24, 2024
* Now a Cel has a z-index property to change the order of layers per frame
* A new doc::RenderPlan class can calculate the order of cels to be rendered
* z-index is saved as a int16_t in the .aseprite files
* This new field can be set/get from Lua with Cel.zIndex
We could provide a "render order" or "z-index" field per cel, where lower values mean to render the layer first, and higher values render the layer overlapping the lower ones (just exactly like CSS z-index).
This field could be added in the Cel Properties dialog:
The text was updated successfully, but these errors were encountered: