When clicking “Show in Explorer” via the right-click menu on a script editor tab:
- If the script isn’t already selected in the Explorer, “Show in Explorer” acts as expected; it will scroll to where the script is, auto open any collapsed parents/folders its inside, and select the script
- If the script is already selected in the Explorer, “Show in Explorer” won’t scroll to where the script is, whether or not its ancestry is collapsed or any other circumstance I can find
I don’t think this is relevant as it seems more an implementation QoL pain/bug, but my system information:
Windows 11
AMD Ryzen 7730U
16GB SODIMM 3200MT/s RAM
512GB SSD NVMe
Integrated graphics - Radeon Graphics
This particular bug/QoL oversight affects my workflow - not in a critical way, but enough to be annoying - as at our studio we have a few scenarios where we’re copying names from the explorer into a script or from UI, and thus have to scroll up and away from the script to look at the name, then to get back in order to open up a child modulescript of the currently selected script or some other child instance the ideal would be “Show in Explorer”, but it’s already selected, thus it doesn’t perform as expected.
I have posted a video below of this happening for reference, showing what happens when the script in question isn’t selected, and when it is.
Expected behavior
I believe this was a QoL oversight or generally just a bug. When clicking “Show in Explorer”, the desired behaviour should always be to actually show the script in the explorer - I’d argue selecting the script itself is a secondary behaviour that is of course still desirable, but with the name of the context option, studio should always actually show and scroll to the item in the explorer regardless of selection state
