Skip to content
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

Color Picker Improvements #2557

Merged
merged 5 commits into from
Mar 21, 2020
Merged

Conversation

Holzhaus
Copy link
Member

@Holzhaus Holzhaus added the ui label Mar 17, 2020
@Holzhaus Holzhaus added this to the 2.3.0 milestone Mar 17, 2020
@Holzhaus
Copy link
Member Author

Holzhaus commented Mar 21, 2020

@Holzhaus Merge? I need this for #2547, just split it off to the PR reviewable and small.

@uklotzde
Copy link
Contributor

LGTM

@uklotzde uklotzde merged commit 31ef3de into mixxxdj:master Mar 21, 2020
@Be-ing
Copy link
Contributor

Be-ing commented Mar 24, 2020

Why is the custom color button not enabled anywhere? I don't think there's a need to make it optional, just enable it. What is the need to hide it in any case?

@Holzhaus
Copy link
Member Author

The already support largest, custom palettes. There is simply no need to open a full-blown QColorDialog when assigning a cue color.

The custom color button will be used for the color replace dialog, where it makes sense to allow picking arbitrary colors.

@Be-ing
Copy link
Contributor

Be-ing commented Mar 24, 2020

Consider a user experimenting with adding another color to their palette but they aren't sure exactly what color they want that to be yet. Currently this user would have to go into the preferences to edit the palette, switch to the main window, right click the hotcue and click the new color, and repeat this for every small adjustment to the color. This would be easier if they could access the color picker directly from the cue menu.

Or maybe a user has some reason for setting a specific hotcue to a color they rarely use. Anyway, the code is already implemented, there is plenty of screen space available for the cue menu, it gives the user much more flexibility, and does not increase the complexity of the code. I don't think there's a good reason to hide the custom color button.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants