Implement sticky scrolling in the explorer

As a Roblox developer, it is currently too hard to click-and-drag objects above very long hierarchies in the explorer. While the explorer window will scroll to where you desire to drag objects, I find that this is too slow and tedious when dealing with hundreds or even thousands of objects under the same parent. Implementing sticky scrolling would address my issue entirely.

RobloxStudioBeta_7itHpExQ8j
The current explorer. There are hundreds of parts nested in a tree of folders and I want to drag a single part up and drop it into Workspace. Without sticky scrolling, I need to scroll all the way up to drop the part into Workspace. Notice how slow I scroll up. Now imagine doing this for many objects.


Here is what an explorer that implements sticky scrolling might look like. Despite having scrolled very deep down into the tree, I am able to access the folders above because they are “stuck” to the top of the window. This makes drag-and-drops and collapsing objects a breeze.

If Roblox is able to address this issue, it would improve my development experience because it would drastically speed up development time and make organizing stuff in my game less of a pain.

14 Likes

Agree this is a pain point, and just from a visual hierarchy understanding, sticky parents would be very helpful.

Just fyi as a workaround, you can click the Parent property in the Properties panel and pick the new parent directly. You still have to scroll a lot, but at least you can use scroll bar instead of having to drag and wait.

You can also use scroll wheel while dragging to speed up the process, but that can be hard to do with some input methods like a touchpad.

1 Like

you can use shift scroll, also while dragging like @BusyCityGuy said.

1 Like

A very big no, just adding more uis to the explorer, instead what u should do, is do the following:

Select the part you want to parent:
image

Scroll to whereever you want to parent:
image

Click Parent property and click on where you want to parent

1 Like

this is a hacky way, but it can sometimes take bit longer than the proposed suggestion if the properties window is minimised (happens soemtimes with big frameworks) or other reasons idk

1 Like