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
Description:
If the drawing order is changed while multiple slots are selected in animate mode, the slot order is incorrect. For example, suppose the slots are lined up as shown in the following image:
Select slot1 and slot2 and move over slot3.
After the move, the order of slot1 and slot2 will be swapped, as shown below:
Expected behavior:
The order does not change among the selected slots. In the example above, the order of slot2 up and slot1 down should be maintained after the move.
Steps to reproduce:
Open the spineboy-pro.spine via the Examples section on the welcome screen.
Switch to the animate mode.
Select the muzzle-ring and the muzzle-ring2 slots under the Draw order section in the tree view.
Drag and drop them to over the muzzle-ring4 slot. Then, you can see the muzzle-ring slot is on top and the muzzle-ring2 slot is below it.
The version of Spine in which this bug was found:
Spine 4.2.19
Description:
If the drawing order is changed while multiple slots are selected in animate mode, the slot order is incorrect. For example, suppose the slots are lined up as shown in the following image:
Select
slot1
andslot2
and move overslot3
.After the move, the order of
slot1
andslot2
will be swapped, as shown below:Expected behavior:
The order does not change among the selected slots. In the example above, the order of
slot2
up andslot1
down should be maintained after the move.Steps to reproduce:
muzzle-ring
and themuzzle-ring2
slots under theDraw order
section in the tree view.muzzle-ring4
slot. Then, you can see themuzzle-ring
slot is on top and themuzzle-ring2
slot is below it.The version of Spine in which this bug was found:
Spine 4.2.19
This issue was reported on the following thread:
https://esotericsoftware.com/forum/d/26117-modify-layer-order-default-order-error
The text was updated successfully, but these errors were encountered: