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
I have checked for similar feature requests and could not find any.
I have made sure this is not an already-existing feature.
Description
I and I'm sure other riggers, would appreciate a way to visualize how the numerical value in "Sorting" equals to the z-order and how the parts are arranged.
Suggested solution
Include some UI showing a bar marked with some values and the associated z-order like how Live2d does it. Or some other UI that can otherwise visualize the sorting values and the z-order.
Alternative solution
Alternatively, you could show a popup when hovering over the Sorting area telling the user that negative values = parts further up front.
I'm sure there are other ways to implement this, but these are the main ideas that come to mind right now.
Additional Context
I would also like a feature to set the sorting order with multiple parts selected all at once, but that may be outside the scope of this feature request.
The text was updated successfully, but these errors were encountered:
Validations
Description
I and I'm sure other riggers, would appreciate a way to visualize how the numerical value in "Sorting" equals to the z-order and how the parts are arranged.
Suggested solution
Include some UI showing a bar marked with some values and the associated z-order like how Live2d does it. Or some other UI that can otherwise visualize the sorting values and the z-order.
Alternative solution
Alternatively, you could show a popup when hovering over the Sorting area telling the user that negative values = parts further up front.
I'm sure there are other ways to implement this, but these are the main ideas that come to mind right now.
Additional Context
I would also like a feature to set the sorting order with multiple parts selected all at once, but that may be outside the scope of this feature request.
The text was updated successfully, but these errors were encountered: