-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
Display settings revert themselves after closing #534
Comments
Hmm, would indeed expect all of this state to be saved with the project. For me this has been the case so far (but I never switch light-mode so maybe that's why I never noticed). |
In my test, all the other appearance settings (zoom, cable opacity etc) were saved, but light mode was not (it reverts to dark mode). Cardinal LV2 23.02 |
this is fixed in latest git and will be part of the next release in 13 days |
This issue is still present in version 23.07 |
I cannot confirm, at least on standalone it behaves as expected. when closing cardinal you should see a line like this:
and that file will have theme mode inside it, like so:
When the ui theme is "light", it will make the dark mode off when starting up a new instance. |
I also cannot confirm. It is fixed for me in 23.07. I tested standalone normal and Mini, and lv2 normal and Mini in Carla host on Linux. |
I meant to say it's the 64-bit VST3 version (in FL Studio 21) that won't save the settings. I tried changing the display to light mode in the standalone version, and it worked fine because the settings were stored in the |
the plugin version will save to fx.json or synth.json or main.json, depending on the variant. |
Fixed in 23.10 release, there was an issue saving user preferences under Windows |
When I enable light mode or change the cable tension, these settings automatically reset after closing FL Studio (v21.0.3)
I tried changing the settings and then saving a project. That still resets the color mode, but not the cable tension.
Affected Cardinal versions: 64-bit Windows VST3 23.02, 5307b9f
The text was updated successfully, but these errors were encountered: