I like the idea of workset and I use it a lot.
Many other tools have the same idea (not oracle tools), i.e. vscode, webstorm, etc.
they keep saving the version somewhere so you can close the program without saving. You choose when to save it locally.
That is what I love this functionality.
The behavior causing issues only happens with pl/sql developer tool. It has never happen in any other tool for different brands.
I work from home so I need to use VPN to connect to the database. From time to time, the connection is dropped or crashed. It should not affect the local workset saving in the local computer, but it does. When Pl/SQL developer detects that it does not have a connection with the database it freezes and windows starts sending popups warning the software lost connection and I have the choice to cancel or wait. Either option will cause the one or more file from the workset to corrupt. Sometimes, the file disappear completely without trace. It is not in the trash can, or anywhere else. I am talking the real file in my local.
Another time, the file still there, but it is empty.
Why workset depends on a database connection? I don't see the reason. I understand when compiling it needs to connect, but to keep a local version?
I have lost so many files. I tried to git commit and keep a version in gitlab, but sometimes I loose hours because this behavior.
The other behavior that it is not fixed, it is the slowness to display all the files, I am talking really slow. I minimize the tool and call it again from the taskbar (it has not been closed, only minimize). It takes long time to display the tool all over again. It does not matter if it is the only tool loaded into the system or not.
This slow display behavior has caused the tool to "not able to communicate" and then the destructive behavior takes place.
I think this needs a fully rework trying to find a solution.
