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

QT_SCREEN_SCALE_FACTORS causes CUE marker display misplacement #10335

Closed
mixxxbot opened this issue Aug 23, 2022 · 17 comments
Closed

QT_SCREEN_SCALE_FACTORS causes CUE marker display misplacement #10335

mixxxbot opened this issue Aug 23, 2022 · 17 comments
Labels
Milestone

Comments

@mixxxbot
Copy link
Collaborator

Reported by: atskler
Date: 2021-02-28T20:31:28Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp1917253
Attachments: QT_SCREEN_SCALE_FACTORS_AND_CUE_MISPLACEMENT.PDF


Setting QT_SCREEN_SCALE_FACTORS causes CUE marker display misplacement on waveforms

See on the screenshots in the attached pdf:
QT_SCREEN_SCALE_FACTORS_AND_CUE_MISPLACEMENT.PDF

Mixxx 2.3.0-beta (build 2.3 r8043)
Operating System: openSUSE Tumbleweed 20210220
Qt Version: 5.15.2
Kernel Version: 5.10.16-1-default
Graphics Processor: Mesa DRI Intel® HD Graphics 3000

@mixxxbot mixxxbot added the bug label Aug 23, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: atskler
Date: 2021-02-28T20:31:28Z
Attachments: QT_SCREEN_SCALE_FACTORS_AND_CUE_MISPLACEMENT.PDF

@mixxxbot
Copy link
Collaborator Author

Commented by: atskler
Date: 2021-03-12T21:42:35Z


Should I re-report this bug under launchpad.net/mixxx/2.3 ?

@mixxxbot
Copy link
Collaborator Author

Commented by: Holzhaus
Date: 2021-03-12T21:53:34Z


No, I just changed the milestone.

@mixxxbot
Copy link
Collaborator Author

Commented by: ywwg
Date: 2021-03-17T13:59:41Z


Yeah I've seen this on windows

@mixxxbot
Copy link
Collaborator Author

Commented by: atskler
Date: 2021-06-02T12:10:03Z


I would like to ask if this bug will be fixed for the 2.3 release?

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2021-06-02T12:41:45Z


Very unlikely because we're about to release 2.3 atm

@mixxxbot
Copy link
Collaborator Author

Commented by: atskler
Date: 2021-06-02T14:00:06Z


Important, so please note it is not just the CUE label, but the complete marker is misplaced on the display. If you jump to a cue, mix will jump to it and will play from it, but the marker will not show the correct position.

.

I would like to add that this bug – at least for me – is quite frustrating, because on my notebook with its standard resolution everything is too small for using mixxx on a live gig: checking the display from about 80-100 cm distance.

Surely I can work around this problem with decreasing the screen resolution.

I think this feature would be important for others, and this problem can impact and mislead others already using this feature - regarding the displayed and the actual cue position.

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2021-06-02T16:15:50Z


sorry, my bad, I was confuding the play position with the Cue marker.

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2021-06-02T21:22:35Z


All waveform markers are affected.
Though there's a difference for text labels and those with icons:
TEXT:

  • text area is cropped
  • stroke is shifted right
    (the longer the text, the further it's shifted)
  • stroke is not painted top to bottom, but stops at
    (top-bottom)/scale factor, so for scale factor of 1.5 it's only
    the upper 2/3 that's painted
    ICON:
  • entire icon is painted
  • stroke is shifted slightly (about half the icon width in Deere),
    though that differs for the CUE and loop_in icon

A wild guess: somwehere in the marker position calculation there's a rounding issues, and appearantly the scale factor is not considered correctly (incomplete stroke for text labels)

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2021-06-02T22:30:26Z


the marker text size is not scaled at all...

got it!

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2021-06-02T22:48:04Z


#3936

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2021-06-02T22:48:26Z


okay, that was easier than I though.
please test!

@mixxxbot
Copy link
Collaborator Author

Commented by: atskler
Date: 2021-06-02T22:54:31Z


Thank you! I will test it once it is merged.

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2021-06-03T00:53:50Z


We prefer testing before merging changes ;)
For each PR there are test builds for Linux, Win and mac (artifacts).
see https://github.com/mixxxdj/mixxx/wiki/Testing for details, especially the backup part.

@mixxxbot
Copy link
Collaborator Author

Commented by: ronso0
Date: 2021-06-03T16:30:45Z


and the fix for pixmap icons
#3938

@mixxxbot
Copy link
Collaborator Author

Commented by: atskler
Date: 2021-06-04T20:10:58Z


Thank You for fixing this issue for v2.3!

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 2.3.0 milestone Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant