Nate, thanks for the fast attention. You guys are really responsive to user inquiries, and I want to explicitly say that I am super impressed and really happy about that.
For my own workflow, what I'm doing can basically be described as frequently switching between several different collections of bones in the dopesheet.
I am frequently swapping between:
- working with a selection group that I created manually by ctrl-clicking in the editor area
- working with a selection group that I created manually by ctrl-clicking in the tree
- working with a selection group that I created manually by ctrl-clicking items in the dopesheet while the dopesheet is locked (I do this a lot)
- working with a pre-created selection group that I saved and loaded using the ctrl+NUM shortcuts
- working with the entire animation by deselecting everything (by pressing SPACE), then locking the dopesheet
Actually checking my workflow, I am also noticing that I'm making heavy use of "Update dopesheet items to selected bones".
Looking at it now, I can see how the list is ordering items by the order they were selected... but it's only doing that consistently when the selection is made while dopesheet is unlocked. I frequently make selections while the dopesheet is locked, and then either unlock/lock, or hit the "Update dopesheet items to selected bones" button.
It appears that if a selection is built (in any manner) while the dopesheet is locked, the "arrange items in the order they were selected" rule no longer applies. When the dopesheet is updated (either by unlocking, or by hitting "refresh") the existing order in the dopesheet is preserved and unecessary items simply are removed.
I think there's also an issue where if:
- a selection is built while the dopesheet is locked, and the dopesheet is updated (selection A)
- a new selection is built, and the dopesheet is updated a second time (selection B)
- all items are deslected and the dopesheet is unlocked
items that were excluded when creating selection B now have their positions in the dopesheet re-arranged... placed at the bottom? I'm not entirely sure what's happening here.
So yeah that's my usage-case. Gotta move on for today, but hopefully this will be helpful.
I think the biggest issue for me is just the inconsistency. I think ideally for me I'd like to have the bones listed in the order they appear in the tree, with perhaps the option to invert the list order if desired.