Skip to content

The names of the skin bone visibility options are unclear and do not clearly reflect selection behavior #1027

@misaki-eymard

Description

@misaki-eymard

The current Tree view option names are difficult to understand, and it is not clear how users can display all keys including skin bone timelines.

The current behavior is as follows:

Case 1
When Hide skin bones and constraints is enabled and Show inactive skin bones is disabled, skin bones are hidden in all views, including the Tree view, viewport, and Dopesheet view.
Skin bones also cannot be selected using hotkeys such as Ctrl + A.
Image

Case 2
When Hide skin bones and constraints is disabled and Show inactive skin bones is disabled, skin bones appear dimmed in the Tree view. However, they are not shown in the viewport or Dopesheet view.
Skin bones also cannot be selected using hotkeys such as Ctrl + A.
It is possible to manually select them from the Tree view, but even if selected, the keys belonging to those bones are still not shown in the Dopesheet view.
Image

Case 3
When Hide skin bones and constraints is disabled and Show inactive skin bones is enabled, skin bones are shown in all views, including the Tree view, viewport, and Dopesheet view.
They can also be selected using hotkeys such as Ctrl + A.
Image

Case 4
When Hide skin bones and constraints is enabled and Show inactive skin bones is enabled, skin bones are hidden in the Tree view, but they are still shown in the viewport and Dopesheet view.
They can also be selected using hotkeys such as Ctrl + A.
Image

The main issue is that Show inactive skin bones does not actually affect only visibility, but also whether skin bones are editable.
Meanwhile, disabling Hide skin bones and constraints makes the skin bone names visible, but does not affect whether they can be selected.

These state changes are difficult to infer from the option names alone, so the behavior likely needs clearer naming or clarification.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions