Skeleton collection
Why is it necessary to click on 'un solo all' before clicking on 'display all' in the skeleton collection? I hope that after clicking on 'display all', the skeleton collection will automatically display all without the need to cancel isolation. Thank you, I have already displayed everything. I definitely hope that isolated collections can automatically cancel isolation,
4 Comments
You'll understand this problem once you've bound your skeleton to the user's skeletal system. You won't even need three months, not even a week, to experience the significant pain. This is because you'll be constantly switching between isolating and displaying the entire skeleton. If I knew programming, I'd easily rank this issue in my top five in terms of importance. It's these seemingly minor issues that impact the user experience. If the functionality isn't used frequently, a little extra complexity isn't a big deal, but for frequently used functions, I really shouldn't create obstacles for users.
Maybe your proposal should be about a new operator that both shows all and un-soloes all, instead of replacing the current behavior:
Solo-ing can be used as a quick way to hide a bulk of collections, while you still hide different sets of collections within the solo-ed ones as you work on the rig. Since solo-ing and regular hiding are used differently, it’s important to keep their operations separate as well.
For example, an animator might solo the legs collections of an armature to focus on tweaking them while hiding a few collections like FK controllers, tweaks or toes to reduce clutter. As they work, they might hide even more parts, unhide others, ... Or go back to the solo-ed state of collections by clicking "Show All". But if clicking "show all" removed their soloing as well, the entire rig would reappear, disrupting their focused view instead of just restoring hidden elements. Keeping soloing and hiding separate avoids these frustrations and gives users more control over their workspace.
Sorry, I completely disagree because if the isolated collection is cancelled after selecting all, I can directly restore it by pressing Ctrl+Z. Ctrl+Z should have this function, right? And if you want to re display the isolated collection, just click on the isolated collection again. The process of isolating collection is already complete enough, but it adds unnecessary workload to the step of displaying all collections. At least in my workflow, the problem you mentioned did not occur at all,I have never worried about the issue of isolated collection. On the contrary, every time I click to display all collections, I have to click to cancel the isolated collection first, which gives me a headache,
Sorry, I want to explain that this is not a new operator, it is just a combination of two operators, but it automatically cancels the isolated set by default before displaying all bone sets.