Closed feldti closed 2 months ago
What version of Jade is this? Did Jade crash and leave the data cleared when you restarted?
The existing code `JadeLoginShell>>saveDataTo: makes quite an effort to avoid data loss (writing to a temp file, then deleting the existing file and renaming the temp file). You might look for the data (mine is at C:\Users\jfoster\AppData\Roaming\JadeData.gss) and make a copy of it for backup.
Long time, but now it seems, that on my machine I can do the following and then the list is lost:
Start Jade - you get the login window Define a source, Do a Login, you get a browser close the login window close the browser window
Start jade, list is lost
if you close the browser window before the login window, the list is NOT lost
The steps to repeat were very helpful. It turns out that we keep the current Transcript window with the login object so you can double-click on the login to get to the Transcript. But if you close the login list with a logged-in session, then it tries to persist the open window. Although that works, we can't recreate the open Transcript window when Jade starts. So since there is an error reading the login list we throw it away and just give a default list. The solution is to clear the session/transcript from the login object that is written to disk so that when we reopen Jade it does not try to recreate the session and transcript.
This still happens for (yesterday quite often) - then all connections and login informations are gone and the list is set to one default entry.
My new hint here is, that I switched yesterday very often between different GS versions and had wrong connection data entered