Beta 12 does not restore the files that were open when it was last open

[paulwas]

Describe the bug
I have 8 files in my sketch. In this case I like to keep all eight files open in the IDE. I think the new drop-down just below the file tabs is a good idea. But every time I re-launch the IDE only the main .INO file is open. I have to then manually open each other file and select "Keep Open".

To Reproduce
Steps to reproduce the behavior:

1. Open a sketch with the Beta 12 IDE that has more than one file in it
2. Open each of the files so there is a tab showing each one
3. Close the IDE
4. Re-Open the sketch and only the main .INO file is open

Expected behavior
All the files I had open when I closed the IDE should be open when I re-launch the IDE

Desktop (please complete the following information):
Edition Windows 10 Pro
Version 21H1
Installed on ‎1/‎16/‎2021
OS build 19043.1237
Serial number 011754392857
Experience Windows Feature Experience Pack 120.2212.3530.0

Note: I've gone back to using Beta 11 because this issue annoys me so much. Overall I love the new IDE and would love to continue using it once this issue has been solved. I'd also be happy if there was a setting to select whether or not you want the IDE to remember the files you had open.

[per1234]

Hi @paulwas. Thanks so much for reporting this bug!

and select "Keep Open".

I can reproduce the bug, but I'm not familiar with this "Keep Open". Where is it?

[paulwas]

Hi @per1234,
When you click on the sketch name just below the tabs, you'll get a drop-down listing each file in the sketch. Once you select one it'll open as a new tab and the text will be in italics. If you click on the sketch name again and select another file, it will replace the last tab you opened. So to keep that tab open (so it's not replaced), right-click on the tab and you'll get a few actions. One of them is "Keep Open".

I like the idea of this new feature, I'd just like it to remember everything so when you re-open the IDE it restores the last state.

[per1234]

Thanks very much for the clarification. I just noticed that we have another report of the bug at #541.

It's best to have only a single issue per subject so we can consolidate all relevant discussion to one place, and that one happened to come in a few days earlier than this so I'll go ahead and close this in favor of the other. But the two issues will now be linked together so all the helpful details you shared will be available for the developers when they are doing their investigation.

If you end up with additional information to share, feel free to comment in the other thread.