Smart Display of the "Update Selection" Panel

[aaa1386]

I'm proposing an idea, but I'm not sure if it's feasible or not.

This idea is related to the "Update Selection" option. Although this feature is useful, it has a drawback: when the selected node has only a few siblings and children, and all of them are visible on the screen, the Update Selection panel still appears. This reduces the user's workspace, and in many cases, displaying this panel via script is unnecessary because FP itself has already displayed all the nodes.

In fact, the Update Selection option is designed to display nodes that are not visible in the FP map due to their distance.

The key question is:
Can the script detect whether all the siblings and children of the selected node fit within the screen or not?

If such detection is possible, a highly practical solution can be implemented:

• Whenever all the siblings and children of the selected node fit within the screen, the "Update Selection" panel should be hidden. Otherwise, it should be displayed.

This approach offers three advantages:

1. Maximizing workspace: The workspace remains uncluttered when the panel is not needed.
2. Enhancing user focus: When the panel appears, the user's attention naturally shifts to it, making node selection easier.
3. Minimizing scrolling: Users will need to scroll less to view the nodes.

Is it possible for the script to make this detection?

[euu2021]

1.41 (script version, not the add-on version). This feature is interesting!

Needs improvement: with node fold/unfold, it automatically hide/shows the inspectors, but only if the fold/unfold makes at least some small change in the map disposition.

I also created a related feature: If a node is not appearing on the screen, it gets a Blue border on the lists:

This way, the user can easily notice which nodes are not on the screen.
I used a blue border, but I'm not sure if it's a good symbology. It gets too much color on the screen, which can be distracting.

[aaa1386]

Blue is a good use, but does it make sense to remove purple?
It seems to have no significant use. Of course, I'm not sure.

[aaa1386]

1.41 (script version, not the add-on version).

The change doesn't work well with right-to-left layouts.
Either way, it's a good start.

[euu2021]

The change doesn't work well with right-to-left layouts.

Which problem happens?

[aaa1386]

Which problem happens?

I'm checking now that it's not because the layouts are left to right.

Sometimes it doesn't work - but most of the time it does. If I notice anything, I'll report it.

I'm having trouble with this map. Can you see if it works on your computer?

ssssssssssss.zip

[aaa1386]

[euu2021]

1.42: removed the purple borders

I'm having trouble with this map. Can you see if it works on your computer?

It's working fine here.

Sometimes it doesn't work - but most of the time it does.

Maybe, it's the fold/unfold, as I mentioned above:
Needs improvement: with node fold/unfold, it automatically hide/shows the inspectors, but only if the fold/unfold makes at least some small change in the map disposition.

[aaa1386]

1.42: removed the purple borders

Thanks for the script update - look at the image. I wish the purple border of the node under the mouse pointer hadn't been removed.

[aaa1386]

When the mouse pointer hovers over a node in the inspector panel, that node becomes active, causing its child nodes to be displayed in the next panel.

In previous versions, a purple border was used to indicate that a node was active, but this feature has been removed in the newer versions. The presence of this purple border is beneficial because:

1. When the purple border appears, the user can be sure that the mouse pointer is on the intended node. This functionality enhances user focus. However, if the border does not appear, the user must not only concentrate on positioning the pointer on the desired node but also pay attention to the appearance of child nodes to confirm that the correct node is selected.

2. Look at the image below; I always set my mouse pointer to a large size. Visually, it is unclear whether Node 1 or Node 2 is active.

3. Adding the purple color to the existing color scheme does not create visual clutter. This color has a completely clear and specific function—so much so that the user does not even perceive it as an additional color.

[euu2021]

1.45: Purple border is back. Now, only in inspectors.

I like the purple border in the inspectors, because it guides the eyes showing which node, among the siblings, was hovered. The eyes can easily follow the path: