-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Rework SetupDialog GUI #7855
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
It might be worth having an "advanced" tab, and hiding away options like sample rate, buffer size, working directory and maybe even audio interface in there. Also, it should be made clearer exactly which options require a restart (maybe a red asterisk next to those options), and ideally a pop-up when you change something requiring a restart prompting the user to save and restart, restart or ignore. The plug-in paths system needs an overhaul, but that’s probably a separate issue.
I think we need to completely stop scrolling over combo widgets from changing the selected option. I looked into this a while ago because I was annoyed by it too. I looked into it a while ago because I was annoyed by this too, and it's a bit annoying to do (requires a whole child class inheriting from QComboBox) but it's possible I propose we have the following pages:
|
Enhancement Summary
The current setup dialog/settings window feel a bit cluttered, especially with all the miscellaneous settings on the very first tab, and no way to search.
Additionally, since there are a lot of settings (particularly in the first tab), the user has to scroll down to view all of them. But, because we have those extremely wide combo boxes, the user can easily accidentally change them as they scroll. And then when trying to put them back to their original state, it can be easy to forget what it was in the first place. Was it "Dual-button" or "Grab Closest"? Or was it "Handles"? I wish I didn't accidentally have my mouse there when I was scrolling!
Additionally, there is no way to reset the settings to the defaults.
Implementation Details / Mockup
I think we should:
Please search the issue tracker for existing feature requests before submitting your own.
The text was updated successfully, but these errors were encountered: