-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
show preferences when configured skin failed to load #3845
Conversation
Alternative: We could switch back to the default skin instead of opening preferences. This saves some work for the user. |
We'd have to inform the user of that behavior with a popup or similar, otherwise they might think its a bug. |
The ideal would probably to have a similar dialog like we have for misconfigured audio settings. So they have the choice between "Exit", "Reconfigure" or "Continue with Default". |
...which requires a more elaborate dialog instead of the standard Ok / Cancel // Yes / No (this fix is adopted from the unconfigured Mic/Passthrough situation) I don't mind. I could deal with it for years. Actually this fix is only for convenience, it neither affects skin developers (as they know what files they were messing with), nor users downloading modded skins (those skins should work to a degree, at least skin.xml should -which is the only file to be corrupt to make skinloader fail). |
Yes we can with the current feature otherwise this PR will just suffer from feature creep again. |
btw another place where we should trigger the same popup |
This is fixed in another way by #3891 |
Sorry, I somehow forgot about this PR. Didn't want to make your work obsolete. |
don't worry. Currently I have neither the motivation nor the time to get this small fix into a mergable state. |
WIP
Addressing a 9 year old TODO
Actually this should happen only with a broken skin from the user directory.
Though, in that case the user has no chance to get back to a working state from within the GUI.
(only by editing mixxx.cfg)
Candidate for 2.3, though when no one wants to squeeze that in right now it can wait for 2.3.1 We got along without it until now.
rebase after #3839 is merged