Make Shape Keys Panel Visible while Pinned Properties Editor for its Mesh Object, for a more dynamic Rigging Workflow while Posing Bones

SUBTITLE: Keep the Visibility of the Shape Keys Panel (a Mesh Data-Block) when Properties Editor is Pinned for its Mesh Object; so that we can Pose the Bones in the Armature Object while watching Driven Shape Keys values change in realtime.

VIDEO EXPLANATION:

ARTICLE EXPLANATION: Hello, Blenderfolks!

I've been Rigging with Shape Keys recently, and I've reidentified a (probably very) old issue that many of us might already have faced with frustration.

In the context of a 3D Character Rigged Model, it's the fact that, currently, we're not able to Manipulate the Bones on Pose Mode for the Armature Object, while simultaneously watching the Shape Keys Mesh Data-Block of the Mesh Object in its own Properties Editor... EVEN if it's Pinned, with the "Toggle PIN ID" Button at the top right corner of the Properties Editor; because it turns out, that the most fundamental Mesh Data-Blocks of conventional Rigging in Blender, which are the Vertex Groups Panel and the Shape Keys Panel (my focus here, although it would be great to solve both limitations at once), loose their Visibility, precisely with the Enabled Pinning... and that is perfectly contradictory, because the description of that Pinning Button is: "keep the current data-block displayed." So, it doesn't deliver what it promises to do!!🙀

Here is a clip I've just recorded that presents the whole thing relatively fast:

The bigger problem of course, is not so much the inconsistency, but is that, precisely, the lack of the proposed (quality of life) 'Cross-Objects' Visibility behavior of fundamental Data-Blocks (such as the Shape Keys in their Shape Keys Panel), is radically detrimental to some of the most conventional Rigging Workflow in Blender! So, it's not perhaps not a "critical" flaw, that would need urgent fixing, like a bug or something similar; but it still might be regarded as a "serious" flaw in my opinion... (think about all the newcomers to Blender... and all the 'oldcomers' as well!); because it doesn't sound too complicated to solve --maybe, it was just forgotten under (virtual) piles of assumedely more prioritary plans for improving Blender features? or maybe, the feature that I suggest, has currently very difficult implications to overcome in terms of the current state of development of Blender UI for Rigging & Animation? I just don't know. Why certain Data-Block need to be conceiled, in an inevitable fashion, while others are, let's say, more 'resilient'? Are they just part of a category like "Shy" Data-Blocks?!? 😹😹😹

Thank you for the attention!