[Fixed] Script tabs closing when returning from play/run

When moving between solo/run in studio some of my open scripts close when returning, fortunately there’s a pattern. Every other script you open will close when returning. This order isn’t affected by the tab order, but the order they’re opened.

The basic repro: Open a new place, insert 2 scripts, Test with play or run and then stop. When returning you’ll find the 2nd script closes.

Numerically naming 6 scripts and opening them in order shows this behavior well:
before

after

I don’t know when this started since I haven’t done much in studio until yesterday, which is when I noticed this issue.

Are the ones that close non-archivable, parented to something non-archivable, or parented to something that has a non-archivable child?

The scripts are just parented to workspace.

Oh, then it’s a different bug from http://developer.roblox.com/forum/studio-bug-reports/15244-non-archivable-objects-close-all-scripts-in-same-directory. Hopefully they both get fixed.

I was able to reproduce your separate bug under all those circumstances you mentioined. While the first 2 are understandable and actually just led me to another bug( described below ), a similar behavior occurs when deleting scripts from the explorer. The last one surprised me.

Related bug: This one isn’t that important, but it’s odd. When deleting all opened scripts from the explorer while in play/run every other script is closed starting with the first opened (as apposed to starting on the 2nd in my other bug). Then when returning all the scripts close.

[quote] When moving between solo/run in studio some of my open scripts close when returning, fortunately there’s a pattern. Every other script you open will close when returning. This order isn’t affected by the tab order, but the order they’re opened.

The basic repro: Open a new place, insert 2 scripts, Test with play or run and then stop. When returning you’ll find the 2nd script closes.

Numerically naming 6 scripts and opening them in order shows this behavior well:
before

after

I don’t know when this started since I haven’t done much in studio until yesterday, which is when I noticed this issue. [/quote]

Oops, that should be fixed now!