In version 1.45, when a user selects a node, if all its sibling nodes or child nodes are visible on the screen, they do not appear in the inspector panels. This behavior is highly effective as long as the user remains focused on the main FP map.
User focus on the main FP map is indicated by the presence of the cursor in this environment. In this scenario, the feature is useful because the inspector panels only become active and display the sibling and child nodes when these nodes are not already visible on the screen. A key advantage of this approach is reducing the need for scrolling to view related nodes.
However, this behavior is not ideal when the user is focused on the inspector panels or the script environment. The indicator of this focus is the cursor being positioned in the script environment. In such cases, the optimal behavior is the same as in earlier versions (1.40 and prior), where sibling and child nodes, or the inspector panel itself, would not disappear.
For example, imagine a user selecting a node within the script environment and temporarily wanting to check its position in the main FP environment, then continuing their work in the inspector panels without leaving them. However, in version 1.45, in some cases, when a user selects a node from within the script, all inspector panels suddenly disappear, disrupting workflow.
The disappearance of nodes within the inspector panel, or the panel itself, is undesirable when the user is fully focused on the script environment, unlike when their main focus is on the FP map.
I am not entirely certain yet, but introducing different behaviors based on cursor position (whether in the FP map or in the script panels) seems like a useful and effective solution.
In version 1.45, when a user selects a node, if all its sibling nodes or child nodes are visible on the screen, they do not appear in the inspector panels. This behavior is highly effective as long as the user remains focused on the main FP map.
User focus on the main FP map is indicated by the presence of the cursor in this environment. In this scenario, the feature is useful because the inspector panels only become active and display the sibling and child nodes when these nodes are not already visible on the screen. A key advantage of this approach is reducing the need for scrolling to view related nodes.
However, this behavior is not ideal when the user is focused on the inspector panels or the script environment. The indicator of this focus is the cursor being positioned in the script environment. In such cases, the optimal behavior is the same as in earlier versions (1.40 and prior), where sibling and child nodes, or the inspector panel itself, would not disappear.
For example, imagine a user selecting a node within the script environment and temporarily wanting to check its position in the main FP environment, then continuing their work in the inspector panels without leaving them. However, in version 1.45, in some cases, when a user selects a node from within the script, all inspector panels suddenly disappear, disrupting workflow.
The disappearance of nodes within the inspector panel, or the panel itself, is undesirable when the user is fully focused on the script environment, unlike when their main focus is on the FP map.
I am not entirely certain yet, but introducing different behaviors based on cursor position (whether in the FP map or in the script panels) seems like a useful and effective solution.