-
Notifications
You must be signed in to change notification settings - Fork 562
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
Use ColorPicker for all color dialogs #3815
Conversation
LGTM! Is this ready to merge? If so, go for it. 👍 |
Merge conflicts have been detected on this PR, please resolve. |
@ferdnyc I resolved conflicts on this one. Can you take a quick looky, and make sure this all still works correctly. If so, let's merge it! Thanks! 👍 |
Merge conflicts have been detected on this PR, please resolve. |
Merging this one as well. I'm gonna be doing a bunch of testing over the weekend, and I really wanted this one included as well. 👍 |
OK, building on #3813 (and, in fact, incorporating it, as it's a necessary prerequisite), this PR makes use of the replacement ColorPicker instead of QColorDialog, in all places where we accept a color as user input.
It also adds
*args, **kwargs
to some of our dialog windows'__init__()
functions, as I noticed they weren't there. As a result of that, we can't (and Qt can't) pass any standard Qt args to those functions, which means you can't do things like parent them.(Of course, the fac that our dialogs aren't parented or parentable is the only thing preventing them from also being modal-by-default, so it could be seen as a happy accident. Then again, it might be a good idea to properly parent them, so that Qt can clean them up for itself.)
Oh, yes, this one finally...
Fixes #3799 and fixes #3798