Godot: Ability to group node icons in Scene dock to drop-down menu.

Created on 20 Jan 2017  路  8Comments  路  Source: godotengine/godot

I like to have layout in which I have two docks next to each other on the right side of the window.
But this layout means these docks need to be thin. And when Scene dock is too thin and nodes in it have too many icons their names are not visible.

scene

So my feature request is a mode in which these icons would be in some kind of drop-down menu. It doesn't have to be default behavior, but it might be a nice feature switchable in the engine settings.

enhancement editor usability

Most helpful comment

What about making them stack overlapping each other by covering half of the icon before it.

 +-+-+-+---+
 | | | |   |
 +-+-+-+---+

When one is hovered it will be brought to foreground. Thus can be clicked safely.

All 8 comments

Maybe a global toggle to hide icons on the tree?
Usually one does not care if node is in group, is a scene, is locked or is visible.

I care about those properties. But they just occupy a lot of space. :)

What about making them stack overlapping each other by covering half of the icon before it.

 +-+-+-+---+
 | | | |   |
 +-+-+-+---+

When one is hovered it will be brought to foreground. Thus can be clicked safely.

Sounds also cool. Or maybe for start just make those icons closer to each other.
Also... when you hover the row with a node a popup with "Instance:" and "Type:" is brought up. I think that value "Name:" could also be there.
I think that these changes wouldn't be much work, but they would help my work flow tremendously.

EDIT: It just came to me, that I'm stupid because name can be deduced from "Instance:" line...

@MrMaidx I mean something like this, maybe with a dropdown menu with multiple selection instead, to check the icons you want to see

hideicons

This issue was solved partially by #8238. Just moving icons closer together is probably enough.

@akien-mga it would be good 2.1.3-rc2 has #8238.
I didn't notice this issue.

@akien-mga @MrMaidx how about closing this issue until somebody suggests better idea or open another issue for it?

Was this page helpful?
0 / 5 - 0 ratings