It’s a great update how ever you can’t tell what scripts are disabled or enabled anymore. They are both the same color.
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:
I believe you’re referring to this:
I don’t think so, I believe it was another reply, maybe from that same staff?
This one
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.
Huge update. Thank you guys so much for this.
I know this is unrelated, but studio takes alot of device memory, and an average roblox developer has multiple studios open. I was wondering if engineers can add something like google chrome, like how when the tab isn’t being used it limits resources or stops its process until opened.
Great update however I would like one thing to be changed,
When adding an instance, the button should directly be next to the Name and not all the way to the right
I like the fact that the new explorer can soft highlight child instances though the current color scheme is a bit confusing. Instinctively i feel as if i am selecting multiple instances when trying to select only one.
I think either way, it’s me.
We are still waiting for finalized colors from our universal design system and we’ll start applying those more broadly. You’ll start to see more color consistency early in the new year.
This could be possible with a new thing we are working on called “Studio Orchestrator” which gives us the ability to have awareness and management of multiple Studio instances. Right now every Studio instance is completely independent with no awareness of each other.
Thanks for sharing! This is a known miss, we’re working on fixing it now.
Any chance you could share a recording of this happening? I’m unable to repro on my end but want to make sure i’m understanding correctly
If you play test while focusing on another window from the same window group as the explorer and then you stop the play test and focus back on the explorer, the scroll bar will be gone until you update something within the explorer like collapsing an instance.
Trying to scroll on the explorer via the scroll wheel (from the mouse ofc) while holding/grabbing an instance will make scrolling pretty unresponsive.
I suspect this is happening due to the held instance being above the explorer so your cursor is technically not within the scrolling frame but rather just the held instance. Scrolling only somewhat works if you scroll while moving your cursor (with the held instance)