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

Shade: Fix invalid "alignment" property for LibraryBPMButton #3786

Merged
merged 1 commit into from
Apr 13, 2021

Conversation

Holzhaus
Copy link
Member

Fixes the following command-line warnings:

Warning [Main]: QCheckBox(0x560803109c10, name="LibraryBPMButton")  does not have a property named  "alignment"
[...]
Warning [Main]: QCheckBox(0x560806004220, name="LibraryBPMButton")  does not have a property named  "alignment"

Fixes the following command-line warnings:

    Warning [Main]: QCheckBox(0x560803109c10, name="LibraryBPMButton")  does not have a property named  "alignment"
    [...]
    Warning [Main]: QCheckBox(0x560806004220, name="LibraryBPMButton")  does not have a property named  "alignment"
@Holzhaus Holzhaus added this to the 2.3.0 milestone Apr 13, 2021
@Holzhaus Holzhaus requested a review from ronso0 April 13, 2021 19:36
@ronso0
Copy link
Member

ronso0 commented Apr 13, 2021

Seems there is no qss way to push the BPM value to the right border of the cell, so basically all those attempts can be removed from all skins. @Holzhaus wanna do it here or should I add that in #3782 ?

btw align right (or align decimal points) of BPM is still open.
https://bugs.launchpad.net/mixxx/+bug/1779775
#2001

@Holzhaus
Copy link
Member Author

Seems there is no qss way to push the BPM value to the right border of the cell, so basically all those attempts can be removed from all skins. @Holzhaus wanna do it here or should I add that in #3782 ?

No, let's just merge this now to fix the warning (makes no visual difference on my system), and then you can make a follow-up PR if you want.

@ronso0 ronso0 merged commit e026044 into mixxxdj:2.3 Apr 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants