v16 Previous windows/tabs not being recovered after restart

[IncredibleMrT]

Hi
Since my move from v15 to v16 a couple of days ago, when I restart I am not being presented with the usual recovery window to open the things I had been working on.

Digging into the PLS-RECOVERY folder for both version 15 and 16, I can the difference is the lack of the cfg file.
In version 15, the recovery files were prefixed 2886434.* (although I expect this number will change often) and suffixed with a counter (001, 002, n) for as many windows as open - then there was a matched cfg file. There's also a bunch of desktop.* files too.

In v16, the files (in this case prefixed 395-[918479]) are there only with the window count suffix - the matched cfg file isn't present.
The cfg files appears to map out and add details on what each file contained - windows name, type, etc.

Attached is a screenshot showing the difference between the v15 & v16 folders.

FWIW, when I first installed v16, it did appear to copy across all my preferences from v15, but not the recovery files - so I copied them across and they all opened without issue.

If it doesn't maintain this same functionality then it isn't really usable as far as i'm concerned - its needed!

I could see a similar post in the beta forum, but I wasn't able to reply against that.

Thanks

 

[IncredibleMrT]

I've copied the format of the original v15 config file and reconstructed for the v16 data and it opened.

I can't be 100% sure that the data stored against each tab is exactly as it was though - my backup rules only saved every 10minutes.

 

[IncredibleMrT]

Can confirm this happened against when I closed PLSQLDev and reopened,

 

[IncredibleMrT]

Again this happened.
Since I switched to v16, I have only had one instance where I closed that it reopened the correct detail. Every other time I would have lost data had I not backed up each window first.

Can anyone shed any light on this?

 

[Lukasz Indeka]

I had similar issues with 16 beta. Maybe this conversation would help.

 

[IncredibleMrT]

Thanks Lukasz. Yours is the post I found when I first encountered the issue.
I would have posted onto that, but it appears to be closed now.

Was hoping Marco might have chimed in by now. Might be a localised issue due to my setup, and if i'm doing something wrong i'll be happy to be told, but for the moment its just functionality that has been in for years that now has gone awry.