Once again, another great update from Roblox, you all are on a roll!
I’d also like to suggest a new “collapse hierarchy when deselecting” option, alongside the new “expand hierarchy when selecting.” Navigating large folder networks with many sub-groups can be very tedious, even with good organization. It often means scrolling all the way back up to collapse folders just to tidy up the workspace. Even using the scroll bar, selecting the folder, and manually using the “collapse” button the problem still exists, especially when you need specific objects selected.
An alternative solution could be a “collapse parent” shortcut that collapses a selected object’s parent without changing the selection. However, a checkbox option for automatic collapsing would be faster and save a shortcut slot. Really hoping to see more fantastic updates like this implemented. Thanks to the Roblox staff working on these updates, you’re doing great!
How does expand hierarchy when selecting even work? What does it do? I’m kinda confused.
Is this a bug? I am confused because what I understood from “Expand hierarchy when selecting” was that it would automatically open the arrow for you upon selecting something with descendants. This does not seem to happen.
I figured it out. There should also be something that collapses the hierarchy when you deselect an object.
Also, pretty sure this was already brought to your attention, but the “Increment names for new instances” option is extremely inconvenient when working with code, and should have an option to have no space in between the number.
Found some more issues, some of them are a little more nebulous though
PluginDebugService currently appears to be missing all of its plugin entries in my current instance of studio (likely same issue below, e.g. it could be that reproducing this only requires doing the search and not just deleting children, but I’m not exactly sure). I clicked an error in a plugin I am working on, right clicked on the open script, and hit “Show in Explorer” and received the following error:
If I search for some parts, press ctrl+a to select them all, then delete them, it causes a lot of instances to appear to not show anything when expanded. For example, if I search ServerStorage.Parts.** is:ValueBase and then press ctrl+a and delete all ValueBase instances, I see examples like this when attempting to expand the object:
It should instead appear like so (I just duplicated the part in the above screenshot and expanded it):
Pressing keys while the explorer is focused does not cycle through the visible instances with names matching the pressed keys. This is currently a big workflow slowdown for some things ime.
Some observations about how this generally works: Cycles over visible entries in order (e.g. does not jump inside of unexpanded instances), always starts inclusively from the selection (I think if there are multiple selections it starts from the lowest one), and resets when clicking away/unfocusing the explorer.
For example, if you have PartA and PartB, typing out part will first select PartA and immediately jump to PartB once B is pressed. If you instead already have PartB selected I believe (haven’t exactly confirmed and might be getting mixed up with other softwares) it only jumps back to PartA if you fully type out PartA (as if the list of entries is cyclic). It sort of seems to function like ctrl+f.
It is pretty common in file browsers (e.g. the Windows explorer) if another reference aside from the original explorer window would be useful. It was a very common way for me to navigate the explorer window rapidly and jump through lots of parts based on their names.
Can you go into more detail about what you use this for? Can you instead use the search? Bringing this back would block us out of things like pressing “F” to focus on the window, and is quite slow.
Just noticed this too, I clicked the + and it appeared on the left side. Did not get fixed when swapping viewports. Don’t know about repro, just annoying.
We are looking into adding an option for the larger padding, as we know that people with certain disabilities like dyslexia and astigmatism may have preferred it, but for now we are trying out this size.
To get these updates, restart Studio until you see Explorer (v0.9) in the title bar.
Not in yet: We have found a fix for the insert object menu, and will be seeing if we can deploy this tomorrow.
I’m experiencing a weird bug with instance visibility after clearing a search query.
If I search for something, and I select the result (only one instance with that name), then I clear my search query, the only thing I can see is the direct path leading to that selected instance. Let’s say I’m looking for a UI button nested inside a few frames. Once I do this, I can only see each instance leading up to that button, other UI elements under that ScreenGui are hidden in the explorer.
This leaves me in a state where I can’t select the other UI instances in the explorer because they are not visible. However, I can still see descendants of other services such as Workspace. Apologies if this explanation isn’t the best.
Why was the indentation sizing changed? I know the new version has indentation guides but the indentation size being the same as the icon size really helped a lot for accessibility for me - so much so that I have gone out of the way to make this type of indentation sizing what I use in other apps like VS Code, Zed, etc. If it was intentionally changed, can we have a setting for it?
I did not know that, thanks for the tip.
I still believe my suggestion could be useful considering multiple button presses, but that definitely saves some time if I don’t need the previous objects selected.
you can see the improvements very fast; expanding instances is very fluid compared to previously where studio would freeze for a few ms before doing so
did get this error while interacting with the explorer in game as well:
Hi, I have been working in studio for 5 years and there is one thing I would like you to implement. Very often I can accidentally drag an object inside another object with my mouse, which is very annoying. Could you make it so that on certain objects you can set a property that it cannot be dragged with the mouse. For example, I click on a script to open it, but it is accidentally dragged inside another script.
