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

regression: waveforms look wrong when enabling / disabling fullscreen #11646

Closed
ywwg opened this issue Jun 11, 2023 · 11 comments
Closed

regression: waveforms look wrong when enabling / disabling fullscreen #11646

ywwg opened this issue Jun 11, 2023 · 11 comments

Comments

@ywwg
Copy link
Member

ywwg commented Jun 11, 2023

Bug Description

This is a regression since the waveform widget rewrite.

image

Resizing the window fixes it:

image

This doesn't always happen, but does reproduce on startup (I have mixxx start up in fullscreen mode).

I tried tweaking the resize event but it didn't help

Version

2.4

OS

Ubuntu 22.04

@ywwg ywwg added the bug label Jun 11, 2023
@m0dB
Copy link
Contributor

m0dB commented Jun 11, 2023

Does it also happen with the allshaders waveform types?

@ywwg
Copy link
Member Author

ywwg commented Jun 12, 2023

also broken with the allshaders type:
image

@ywwg
Copy link
Member Author

ywwg commented Jun 13, 2023

to me it looks like this is not an issue of the size of the widget, but the position. The waveform appears to get the wrong x,y origins.

@m0dB
Copy link
Contributor

m0dB commented Jun 23, 2023

I can't reproduce this on macOS, but I feel like I am missing something. So to be sure, are these the scenarios?

  1. You are in non-fullscreen, you load a track which is shown correctly, you select full screen, waveform is now displaced
  2. You are in fullscreen, you load a track which is shown correctly, you select full screen, waveform is now displaced
  3. You start the app in fullscreen, you load a track, waveform is displaced

Where 1 and 2 do not always happen, but 3 does. Is that correct?

@foss-
Copy link
Contributor

foss- commented Jun 24, 2023

Also unable to reproduce on macOS 13.4.1.

Maybe Linux only bug?
Is the problem reproducible in all skins or limited to a specific skin?
Is the problem reproducible with all waveforms or limited to a specific waveform?

@m0dB
Copy link
Contributor

m0dB commented Jun 24, 2023

From the screenshots I get the impression that it actually behaves slightly different depending on the waveform type.

I will try to reproduce and debug this with Linux somewhere next week.

@Swiftb0y
Copy link
Member

Swiftb0y commented Jun 24, 2023

also broken with the allshaders type: image

what Linux distribution is this? The window decoration looks like Windows 10...

@ywwg
Copy link
Member Author

ywwg commented Jul 4, 2023

It's ubuntu 22.04.

@JoergAtGithub JoergAtGithub added this to the 2.4.0 milestone Jul 16, 2023
@JoergAtGithub
Copy link
Member

@ywwg You seem to be the only user experiencing this issue. Could you provide any additional information to reproduce it?

@ywwg
Copy link
Member Author

ywwg commented Jul 27, 2023

I believe I have seen this with both the qt6 / opengl flags and without, which leads me to believe this is not a regression and is just a quirk on my system / OS. If no one else can reproduce, I am ok closing the bug. It is cosmetic and not hard to work around.

@ywwg
Copy link
Member Author

ywwg commented Aug 4, 2023

closing as not-reproducible for anyone else

@ywwg ywwg closed this as not planned Won't fix, can't repro, duplicate, stale Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants