-
Notifications
You must be signed in to change notification settings - Fork 225
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
Remove --cleanuplegacyfadersettings command line option #2850
Comments
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Jul 29, 2023
5 tasks
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Jul 30, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 1, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 3, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 15, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 23, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 25, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 28, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 28, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 5, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 12, 2023
5 tasks
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 18, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 27, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 27, 2023
pljones
added a commit
that referenced
this issue
Oct 2, 2023
…fadersettings #2850 Remove --cleanuplegacyfadersettings command line option
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#2839 created a temporary command line option that performed a clean up of corrupted saved fader settings. This only needs to be done once per file and users are expected to recover their settings when taking the upgrade from 3.9.0 to 3.9.1.
As part of a later release - after 3.10.0 - this temporary option and the supporting code should be removed.
The text was updated successfully, but these errors were encountered: