-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[MU4 Issue] Regression: opacity control missing in color picker #13652
Comments
I want to work on this, can you please assign me this issue? |
I was able to add the alpha channel in the colour picker but the task also said that the solution should be smart enough to realise when alpha is 0 and set it to max (atleast that's how I interpreted the problem). |
How about https://doc.qt.io/qt-5/qcolor.html#setAlpha? |
Thanks a lot, this is what I needed. |
issue_13652_fix.mp4 |
Describe the bug
MuseScore 4 lacks the opacity control in the color picker - needed for creating highlighter effects
To Reproduce
Steps to reproduce the behavior:
Expected behavior
An opacity control is needed to create translucent effects, such as mimicking a yellow highlighter pen
Screenshots
![image](https://user-images.githubusercontent.com/1799936/194440528-9a4a0ebb-dc2a-4e42-a88e-3b197a0bb46e.png)
This is how it looked in MuseScore 3, and shows how the feature was commonly used by educators:
Platform information
Additional context
In MU3, it was very annoyingly necessary to explicitly set this to 255 if you wanted to actually see the background color at all - the default was 0. Glad to see that opening this dialog now sets the color to opaque. But, there still needs to be a way to set it to intermediate values like 127. And, a small complication - that value, once explicitly set, should remain set and not get arbitrarily changed to 255 every time you open the dialog. So, whatever magic happens to force the opacity to 255 upon setting a color, should be smart enough not to do this if there is an explicit opacity value already set.
The text was updated successfully, but these errors were encountered: