Replies: 6 comments 3 replies
-
We probably have enough space to split them into separate docks now. I've never been too fond of the "subtab" UI within the Node dock either, as it's not very obvious that these two buttons effectively act like tabs (since they don't look like tabs). However, if we split them into separate docks, we won't be able to offer a single tab where you can view both at once. You could always choose to use them as separate docks in separate areas, but this would mean they'd collectively take up a lot of space (the editor only has 8 dock "slots" that can be seen at a time). That said, this is only really practical if your dock is really tall – I doubt this is viable on 1920×1080 displays at 100% scale, for instance. |
Beta Was this translation helpful? Give feedback.
-
In my opinion, groups should be moved to project settings and work similar to layers. They should be assigned from the inspector. |
Beta Was this translation helpful? Give feedback.
-
I agree with much of what you said... that's why we need an open discussion about this. The 8-slots design is both clean and limiting... we need to find something that works in combination with that line of design. Finally, to be honest, even in my old 1366x768 notebook I'm still into proposing a new design for this. edit: to add, in practice the 8-slot is only 4-slot if your screen isn't big enough |
Beta Was this translation helpful? Give feedback.
-
Moving signals and/or groups into the inspector and maybe adding a project settings panel for their project-wide options is a very good idea in my opinion... thinking fast, the main problem with this is that it's kinda invasive/strong modification over the ux and the workflow. However, it expands it's horizons too. That said, I think I understand why node and inspector evolved to being separated tabs. all you have in the inspector is (broadly speaking) a single resource (or at least can be treated as a resource) and the node tab stuff is kinda the stuff what doesn't fit into that resource. In some point the design is clashing with user experience, that's why we are debating here. |
Beta Was this translation helpful? Give feedback.
-
i really wish this were the case, i honestly don't see any reason for them to be sub tabs under the node tab. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I came from here godotengine/godot#27629
It's a pity this didn't transcend, because it was a very interesting issue.
Nowadays it seems like this:
The why signals and groups deserve better places in the Ui (or at least an option to have the legacy/new) are several:
Proposals? The first options that come to my mind are:
Edit: fix redaction fault
Beta Was this translation helpful? Give feedback.
All reactions