Project state not being saved on project change

[dunkers]

If one has a project open and then switches to a separate project, the state of the first project is not saved to disk until SE closes. To demo this, follow these steps:

1/ Open project1 and change the displayed edit file, moving the cursor, etc.

2/ Switch to another project without closing SE.

3/ Run up another instance of SE and open project1. The expectation is that the edit file and cursor position should be as it was left in step 1, but in fact it's as it was when the first instance of SE opened the project.

4/ Close the second instance of SE, then the first instance.

5/ Run up SE and open project1. The edit file and cursor position are now in the expected post step 1 state.

[Lee]

File positions are not stored with workspace history, they are stored with the user configuration directory.  And it is not serialized until application shutdown, which does confirm what you observed when you changed instances.

I can add the feature request in our tracker for future consideration, see if we can an optional behavior to include save/restore file positions per workspace. 

[dunkers]

Ah! I can see pros and cons for either case (storing as per workspace or user). The option would be good, but I wouldn't class this as an awfully important feature.

Thanks

[dunkers]

But I think there's a bug somewhere here. One thing I just noticed is that my project now has more files open (tabs) than it did last time I used it. I've had this before, but since I wasn't checking every time, and I often have lots of files open, I couldn't be sure. But this time I know that I had only 5 or 6 files open and now I have so many the tabs get the scroll arrows.

I think my original files are there, plus what seems to be a set of files that weren't open, and this second set seem to be the same ones every time.

I realise there's not a lot you can do or say about this without hard repeatable proof, but it would become a non-problem if we could save/restore sets of open files.