I’m not sure what feature you’re referring to, can you show in the old Explorer what you’re doing that you can’t anymore?
1 Like
Ctrl + Z: Undo
Ctrl + Y: Redo
Also this Next Gen UI is gonna be forced in the future, like it or not, you’re gonna be forced to use it.
1 Like
Here it is.
You are able to do it without the new gen explorer.
Now you cannot.
That is the problem with this plus please add back the redo/undo buttons because they are more easier instead of doing ctrl + z undo ctrl +y redo according to Karlos. And you cannot scroll to the left or right in the Explorer.
1 Like
you should be able to press CTRL and then select the other model
Box select is coming in an update that will be out before release.
1 Like
I am really glad to hear that staff. Wish smooth scrolling was still in there because it looks problematic to me and me having to click on the scroll button just to go to a certain part that cant be seen with the non-smooth scrolling anymore.
In fact–box select is out now in v0.18.
1 Like
When dragging an instance in the explorer I cannot scroll up and down in the explorer when the mouse is still. I have to move the mouse around in circles over the explorer in order to scroll. I also feel like automatic scrolling should happen whenever a dragged element is moved to the top / bottom of the explorer tab. This doesn’t seem to happen for me either.
I have a fix for not being able to scroll while dragging in next week’s release.
1 Like
i can see that there is nothing about the next gen properties tab are you planning to release it with the next gen studio without a beta release ?
To me, custom tabs don’t sound like multiple quick access toolbars, they just sound like more tabs. Don’t get me wrong custom tabs sound amazing but quick access is still super useful to have because you don’t have to switch tabs to access it. The whole point of quick access is to have useful things like plugins a single click away without having to navigate to your plugins tab. What you are describing is just the same thing but with a custom tab. And I understand that the point of a custom tab is to group tools together that you frequently use for some particular workflow, but I Imagine for some things it isn’t practical to do so all in a single tab (especially with how much padding you guys are putting between buttons, but you mentioned working on that so that’s good). Having new tools and capabilities in studio is great but removing widely used features to get there isn’t the way to go in my opinion. Some things I’d just like to have access to no matter what tab I’m on, without having to switch tabs or put that tool into every single custom tab.
I would be very vey sad if quick access were to disappear behind more menus.
No, we focused on getting the Explorer shipped first so that we could take lessons from that to use in the Properties. We have an early prototype codebase for the Properties that we used to prove out our implementation plans for it but we haven’t shipped that yet and it will have its own beta period.
2 Likes
Since Explorer is nearing the end of the beta (well, at least it’s pretty usable with recent bug-fixes), when do you guys see the properties tab entering the implementation and the beta phase?
2 Likes
Properties beta will be whenever it’s ready, probably still months away.
3 Likes