Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bone Re-Ordering Feature Request #116

Closed
JArmstrongArt opened this issue Oct 12, 2022 · 2 comments
Closed

Bone Re-Ordering Feature Request #116

JArmstrongArt opened this issue Oct 12, 2022 · 2 comments

Comments

@JArmstrongArt
Copy link

I don't mean to come off entitled or punching above my weight, but I had an idea to make bone re-ordering a bit more convenient.
image
The arrows on the right-hand side work well enough to swap bones, but moving specific sets of bones a long way across the list takes a long time and is actively quite difficult to focus your eyes on doing.
My idea is to add 2 things, maybe just one of them or maybe both:

  1. Put text entry indexes to the left of each bone name. If you change the number in the field, the list readjusts to the new index you typed in for that bone.
    image
  2. Make it so that when you click the arrows on the right whilst holding shift, the bone those arrows belong to moves either all the way to the top of the list or all the way to the bottom of the list respectively.
@ScanMountGoat
Copy link
Owner

This is related to #85. The real issue is that we don't have a good understanding of what the requirements are for ordering bones in custom skeletons. Bone ordering should ideally be handled at export time from applications like Blender. Manually ordering entries isn't a big priority at the moment.

@JArmstrongArt
Copy link
Author

Oh okay, thanks for the insight. And yeah, as of a few hours ago, Carlos' tool has ben rectified to export swing bones where they ought to be, so it is significantly of less importance. Do consider my design if the priority and reason presents itself to be implemented, but I consider this issue closed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants