-
-
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
Tango: style Quick Effect selector #4503
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rebase this to main. Without a rebase we see rebased commits from the already merged PRs twice in the history.
The rest looks good. |
That's how I planned to do it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The removal of the border and making the background identical to the surroundings makes it hard to tell that the comboboxes are comboboxes. This PR is a step backwards IMO. Can you explain why you think these changes are an improvement?
These commits where identical, inclusive their history. Here they are almost identical, with a different commit hash. |
WEffectChainPresetSelector { | ||
background-color: #252525; | ||
color: #888; | ||
WEffectChainPresetSelector { | ||
/* blend with the mixer backgrpund */ | ||
background-color: #333; | ||
color: #aaa; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert this.
IMO its still visible that the effect name is a clickable combobox because of the "down-arrowhead" next to the name. |
I think it mainly saves screen space that would otherwise be used by margins/padding/borders. I'm also torn on this, because I think it space-efficient and looks good, but on the other hand it's less easy to discover. Maybe we can consider adding borders and reducing font size instead. |
If we talk about discoverability, I think thats fine too. It's not an essential feature that you need to see understand and instantly (like the playbutton for example). Its not like its deeply buried in menus (unless we hide it using a skin or preference option, which is not good idea IMO). |
I agree that it isn't crucial that this is super easy to discover and even with this change it isn't too hard to discover, but still, this makes it harder to discover and I don't think there was a problem with the styling before. |
I guess its a personal preference call, and I prefer this. Should we decide via a quick poll? |
I would like to hear @ronso0's motivation for this change before jumping to a vote. |
My motivation for this plain effect selector
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The previous implementation was quick and dirty and always added extra row to the deck. Though, I can try to squeeze out a few more pixels for the selector. |
Note: the screenshot was made with #4532 |
marked as draft because it looks like I broke the fx units. I'll remove the extra tweaks and add the chain preset button styling asap. |
I wouldn't be opposed to that last screenshot, though I still prefer how it is currently in the main branch. |
In another PR I'll make the fx unit menu more discoverable (WEffectChainPresetButton), the arrow was just a quick shot, too. I used the gear icon (skin settings) for that in LateNight and it makes more sense than the down arrow. |
Why did you put the PFL button the same height as the dropdown? Wouldn't it make more sense to make the vumeter shorter to put the pfl button horizontally aligned with the filter and gain knob so there is more space for the text in dropdown? |
Yes, that would look better for that one configuration.
Tbh I'm not motivated to work on that right now. The Deere implementation is still overdue, LateNight still needs the chain menu button... |
That said, I'd like to merge this now and me or anyone else may propose improvements later on. |
Thanks for the explanation. Sure we can merge. |
@Be-ing already agreed to the new implementationearlier so I don't think we need to wait for his formal approval. |
He also recently announced to abstain from contributing to mixxx for the foreseeable future, I don't think he'll care to review/approve this PR because of that. |
pa-ping... |
Alright, shall we merge then? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 👍
based on #4501
updated: