-
Notifications
You must be signed in to change notification settings - Fork 386
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
[Bug]: "Open library on start" toggle doesn't acculy make it open library on start #797
Comments
I don't believe this was ever fixed #725 (comment) |
weirdly tho it does seem to be setting the flag in where ever it stores the flag, except.. the only thing that's detecting the flag is the older version of tag studio, which is funny |
i cant seem to recreate this, the steps im interpreting are:
however following those steps results in the previous library being open on startup |
huh, maybe the important part for this bug that i converted the library over from json |
I was able to reproduce this when starting from an old preferences file, but as soon as I toggled the setting on and off it just worked from there. For whatever the |
Can confirm, it didn't work until I toggled it ^^ |
I think this can be closed, perhaps this needs a change in the migration code though? |
I wouldn't mind closing the issue - also this setting isn't affected by the sql migration so any effects have been separate from the changes to other parts of the codebase |
Checklist
TagStudio Version
9.5.0 prerelease 2
Operating System & Version
Win11
Description
currently the new "open library on start" toggle doenst open whatever library you turned the toggle on for it to auto open when you reopen tag studio (assuming thats how your intended to use it anyway)
Expected Behavior
toggling it on, on any library should make it auto open that library on next boot of tagstudio
Steps to Reproduce
it is on by default in the current version so i suppose just open any library and then close the studio and then reopen it and it doesn't open library again like its supposed to
Logs
No response
The text was updated successfully, but these errors were encountered: