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

Tuner Slider GUI Window Size Scaling Issue #418

Open
3813127458 opened this issue Dec 29, 2023 · 10 comments
Open

Tuner Slider GUI Window Size Scaling Issue #418

3813127458 opened this issue Dec 29, 2023 · 10 comments

Comments

@3813127458
Copy link

Qucs-S 24.1-7df0e3e9
Linux 6.6.8-2-MANJARO
GNOME 45.2
Wayland

The tuner slider GUI window shows uncomfortable window size auto scaling.

Potential solution: pre-asses parameters field length and change GUI window size only if it is necessary.
The solution need to be tested with e.g. 10 tuner slider in operation parallel.

Tuner_Slider_GUI_Window_Issue.webm

RTF_N7_master.zip

@ra3xdh
Copy link
Owner

ra3xdh commented Dec 29, 2023

I cannot reproduce these issues using X11/KDE or Windows. Need to wait for someone who can debug and provide a patch for Wayland.

@3813127458
Copy link
Author

I can confirm that it works seamless on:

MANJARO KDE Frameworks Version 5.113.0
KDE Plasma Version 5.27.10
Qt Version 5.15.11

@3813127458
Copy link
Author

I did test Debian 12, Gnome Desktop on Wayland, and it works without any problems.
Therefore, it is probably a specific problem of the actual Manjaro/Gnome/Wayland desktop.

@ra3xdh
Copy link
Owner

ra3xdh commented May 23, 2024

I have tested the Wayland+Qt6.7.0 platform. I still cannot reproduce exactly the same issue, but the other tuner window size issues appear time to time. It's starnge, but the Windows build using the same Qt version is not affected.

@ra3xdh
Copy link
Owner

ra3xdh commented Jun 2, 2024

@3813127458 I still cannot reproduce the bug exactly as on your screen recording, but another tuner window size issues appear on my system. Do you see the behavior as in the attached screencast? Only Wayland is affected. The X11 and Windows work as expected using Qt6.
Screencast_20240602_090232.webm

@ra3xdh
Copy link
Owner

ra3xdh commented Jun 4, 2024

It seems the QWidge::adjustSize() (tuner.cpp line 749) doesn't work properly for Qt6 using Wayland backend. Only hardcoded minimum size for TunerElement helps. I failed to provide a fix for this issue.

@ra3xdh
Copy link
Owner

ra3xdh commented Jun 9, 2024

The following solution for these issues is possible:

  • Hardcode size hint for TunerElement class. This makes the tuner dialog autoscaled properly on Wayland
  • Wait for the next Qt6 version. There exist probability that this issue is related to some bugs in QtWayland backend, because X11 and Windows works properly.

If this issue will be not self fixed after the next Qt6 update until the Qucs-S release (planned for September), I will accept the second solution.

@3813127458
Copy link
Author

Maybe this was a specific issue of MANJARO / GNOME 45.2 / Wayland.
At the moment I have no MANJARO / GNOME / Wayland platform available for testing.

The latest Opensuse / Tumbleweed / KDE / Wayland and X11 works fine.

@ra3xdh
Copy link
Owner

ra3xdh commented Jun 9, 2024

KDE6+Manjaro+Wayland has not exactly the issue from the first post but this issue instead: https://github.com/ra3xdh/qucs_s/assets/4920080/3a27311c-0bdf-404d-b77f-8a9d61a9bc39 Could you reproduce this using OpenSUSE+KDE+Wayland?

@3813127458
Copy link
Author

Yes, I can confirm, that the cursor goes to window scaling mode after selecting a value to be tuned:

2024-06-09.10-50-37.mp4

Qucs-S 24.2.0

Operating System: openSUSE Tumbleweed 20240607
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4400

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

2 participants