Skip to content

Remove QSBackgroundView #2635

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

Merged
merged 2 commits into from
Feb 16, 2022
Merged

Remove QSBackgroundView #2635

merged 2 commits into from
Feb 16, 2022

Conversation

pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented Feb 13, 2022

In the same light as removing QSGlossyBar, this removes QSBackground view, and its custom 'fancy' drawing.

Edit: removing the view was a bit premature, it is actually used by a couple of plugins. Instead, I just removed the code draws the gradient backgrounds.

It makes the Results Window more 'flat' and hopefully more 'modern':
Screenshot 2022-02-13 at 21 45 51

I also properly bound the results view header/footer text colour to the appearance prefs, fixing #1235

I'm a little bit more confident that these changes may help with the Catalina/Big Sur colour problems. Less archaic code is good, right?! :D

@skurfer
Copy link
Member

skurfer commented Feb 16, 2022

The contrast isn’t ideal depending on the chosen colors, but it’s still a big improvement.

@skurfer skurfer merged commit 89cf451 into master Feb 16, 2022
@skurfer skurfer deleted the qsbackgroundview branch February 16, 2022 03:11
skurfer added a commit that referenced this pull request Feb 16, 2022
@pjrobertson
Copy link
Member Author

The contrast isn’t ideal depending on the chosen colors, but it’s still a big improvement.

Agreed. I'll take a look at tweaking the Default QS colours. It may make sense to spruce up QS's colour palette based on the new logo anyway.

@pjrobertson
Copy link
Member Author

pjrobertson commented Feb 16, 2022

@skurfer - if you're updating the CHANGELOG - make sure to pull --rebase first - I've just updated it

EDIT: You're one step ahead. Already done it I see ;-)

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

Successfully merging this pull request may close these issues.

2 participants