Create a new project
Create a Frame
Create a LocalScript
Set a breakpoint on the first line of LocalScript
Run
When it pauses on the breakpoint, Ctrl+p to find and type frame
Hit Enter to select the object. The ‘Properties’ are shown, but Explorer window is not:
It’s happening both with Explorer beta on and off
I know why this is happening and maybe already landed a fix for it in this/next week’s release. I’m investigating now.
To be clear, this only happens when debugging?
Yes
Yeah, looks like my fix is going to apply to this too. Keep an eye out in the changelog.
Just to add, this problem also occurs when the script stops at an error line.
Sorry, but this is the behavior I’ve been criticizing for a long time.
Fixes to a reported bug in the forum should be posted in the same original forum thread.
Leaving developers to find out on their own if a bug has been fixed is incorrect and unproductive, as many developers can spend months (or even years) using an unnecessary workaround, just because they were not advised of the correction in the right way (i.e., in the thread that originally reported the error).
That is fair enough, I am just not confident I will remember this thread. I’ll set a reminder to myself.
Just to point out, with this current bug it is IMPOSSIBLE to search for objects inside Explorer, while there is an error or debugging (even trying to manually open it with the mouse):
So, this is URGENT! 
I changed the title as this is a GENERAL BUG in the Explorer window while debugging.
Should be fixed now, let me know if it is not.
Fixed.
Thanks for letting me know.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
