I know…
But why not make it so:
If you use the old “classic” style, the Explorer will be like everything else.
And if you use the beta studio UI the explorer will have the modern design?
It’s a known bug–it’s because you’re starting in the blank space where there are no rows. If you instead start your selection from the right of a name, it will work.
Can you file this as a bug report?
1 Like
Having issues where randomly some shortcuts like ctrl+c, ctrl+v, and Del, don’t seem to be doing anything in the explorer until I swap to a viewport tab or manually select some of these options in the ribbon:
Seems to trigger randomly when swapping scripting tabs and alt tabbing
1 Like
Hi, thanks for the feedback!
The Explorer should auto expand the collapsed hierarchy when you insert an object into it. If not, could you try restarting the Studio and see if this still not working for you?
Can we have a way to shrink the displayed items in the explorer as an accessibility setting? We’ve lost a bit of valuable screen real-estate making them bigger and I have to scroll a lot more to reach my target instances
1 Like
Try closing all Studios and reopening until you see any version number in your Explorer title bar (at the moment, should be v0.23).
Have you guys fixed the hovering problem that causes the Instances with children to expand in the explorer?
1 Like
Just came here to ask: do not rush the removal of the QT Explorer.
This is clearly not as robust and battle-tested as it needs to be. This is a fundamental part of Studio, there is no margin for error.
I’ve used it for 5 minutes and it managed to:
- Stick my viewport camera pan (right click).
- Had this overlay deliberately follow the height of my mouse (in the the rest of Studio, but even when I’m in VS Code, Discord, Chrome, etc.). Could not get rid of it whatsoever.
- Confuse my understanding of selection with a tint on the descendants? It needs more contrast between the main selection and its descendants.
- Inconsistent with the rest of the Studio UI. It looks ridiculous next the the Properties.
- Text sharpness is no good, especially considering the font is larger.
6 Likes
When editing ObjectValue’s Value and both Explorer and Properties are in the “same window” (one has to switch between them using the tabs), the select mode gets cancelled once clicking the Explorer tab.
1 Like
It doesn’t work. It still doesn’t open automatically.
Do you have “Select object after Insert” turned off in the Insert Object popup?
Oh, thanks! I don’t know why that wasn’t turned on earlier. The update must have changed that.
3 Likes
Hi, thanks for sharing the video!
We are looking into the shortcuts problem now.
This is just the same but just different colors and new buttons lmao.
The new explorer is written in Lua rather than using the Qt library and C++ (to my knowledge). It’s much faster, and remade to be more modern.
2 Likes
I love the fact you listened to the community and increased the information density! I’m hoping to see this change for the rest of the next gen UI.
Also, a setting to change the spacing between instances would be pretty nice!
3 Likes
Hard agree on this! Heavily relied on this feature a lot before.
1 Like
This might be because you have the “expand hierarchy when selecting” setting off in the 3 dot menu, and you are clicking around in the viewport. This blue selection outline lets you know what what you have selected is within a certain hierarchy in the explorer.
1 Like