-
-
Notifications
You must be signed in to change notification settings - Fork 7
Feature Request: Last session per User #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I agree that the last-used session being stored as the default on the login screen would be a nice feature. As it is, it appears to default to whatever session file is alphabetically first in the |
Currently it should already store the last user and the last session, but the session is not stored on a per user basis. |
Ah, I see. Thank you for the clarification; I do see that file and after looking at it I understand what is happening.
I was testing something unrelated, and had multiple Since this kind of setup would never have a practical reason to exist on an actual user's system, this seems like a non-issue in my case. Apologies for hijacking your issue @loaidheach, at first glance I thought you had made the same observation that I had, but now I see my thing is totally unrelated. Thanks again for the tip on |
Due to an influx of real life job, I haven't had much time lately. I'll try to get down to it soon. |
No worries and thanks for creating nwg-hello at all! I should have some time to look at it tomorrow. I will implement it tomorrow and create a pull request. |
It would be nice if the last session could be stored on a per user basis.
I haven't looked at the code in detail, but in looks like it should be relatively easy to implement. Apart from changing the session when the user select is changed (via
notify::selected
), thecache.json
would need a different format, e.g.The text was updated successfully, but these errors were encountered: