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

Size of viewpoint #304

Closed
nemanjan00 opened this issue May 31, 2022 · 12 comments
Closed

Size of viewpoint #304

nemanjan00 opened this issue May 31, 2022 · 12 comments
Labels
User Interface Look and feel of the program

Comments

@nemanjan00
Copy link

Describe the bug

20220531_10h54m54s_grim

Viewpoint does not resize when I click with resize cursor and drag to resize

To Reproduce

Open program and try to resize

Expected behavior
Viewpoint should resize

Screenshots

20220531_10h54m54s_grim

Computer environment (please complete the following information):

  • OpenHantek version: b46ab64
  • OS: Linux
  • Distribution, version: Arch with Wayland
  • Video hardware: Intel® UHD Graphics for 8th Generation Intel® Processors
  • OpenGL version: Mesa 22.1.0-1
  • Qt version: Qt 5.15.3
  • C++ compiler version: gcc 12.1.0

Scope device (please complete the following information):

  • Device Hantek 6022BE
  • Program top line OpenHantek6022 (3.3.0) - Device DSO-6022-BE (FW0210)
  • Input signal: no
  • Probe setting:no
    Additional context
OpenHantek6022 (3.3.0)
Graphic: 4.6 (Compatibility Profile) Mesa 22.1.0 - GLSL version 1.20
@Ho-Ro Ho-Ro added the Graphic Graphic / OpenGL related issues, artifacts or blank screen label May 31, 2022
@Ho-Ro
Copy link
Member

Ho-Ro commented May 31, 2022

This is such an obvious error, but the first time it has been reported here. I suspect that it is caused by your setup, especially using Wayland.
Did you try the options --useGLES, --useGLSL120, or --useGLSL150?

@nemanjan00
Copy link
Author

I am not in front of that laptop right now. Will be testing it later.

Interesting thing is that on another computer, with setup that should be the same I have it working properly...

So it probably is issue with my setup...

Thanks for quick reply

@Ho-Ro
Copy link
Member

Ho-Ro commented May 31, 2022

If you use this erroneous laptop, please also check whether the sub-windows (e.g. the setup window) show comparable behaviour. But I suspect that DsoWidget (the black part of the scope) is causing this issue.

@nemanjan00
Copy link
Author

Hello,
There is similar behavior in other windows too

20220612_14h17m31s_grim

@nemanjan00
Copy link
Author

Ok, I figured it out. It is related to QT theme I used

@nemanjan00
Copy link
Author

Just in case you want to take a deeper look, since it is quite popular theme framework, it is Kvantum

@Ho-Ro
Copy link
Member

Ho-Ro commented Jun 13, 2022

Thank you for this info, I can confirm this issue with Kvantum and Kvantum dark (never used this theme before). A simple workaround would be to select "Fusion" style and "Dark" theme in menu Oscilloscope/Settings/Colors.

Ho-Ro added a commit that referenced this issue Jun 14, 2022
switch to the dark "Fusion" style when "kvantum*" is the system style

Signed-off-by: Martin <Ho-Ro@users.noreply.github.com>
@Ho-Ro
Copy link
Member

Ho-Ro commented Jun 14, 2022

There is now a "hack" (c0a7fac, also latest unstable) that switches to the dark fusion style when it detects "kvantum*" as the system style - you may have to manually correct the disturbed look once.

@Ho-Ro Ho-Ro added User Interface Look and feel of the program and removed Graphic Graphic / OpenGL related issues, artifacts or blank screen labels Jun 14, 2022
@jvandenbroek
Copy link

Thanks, I had the same issue. Not sure about that hack @Ho-Ro , I've installed the git version from AUR and still had this issue with Kvantum theme.

@Ho-Ro
Copy link
Member

Ho-Ro commented Aug 5, 2022

@jvandenbroek Which version does the program show in the top line?

image

If it is this AUR version then it is very outdated (Last Updated: | 2021-11-19 13:14 (UTC)):

image

based on this commit - more than 100 commits ago:

commit e7f7a5d75054590ba0085a8a63bf28108ce73e21
Author: Martin <Ho-Ro@users.noreply.github.com>
Date:   Fri Nov 19 13:03:09 2021 +0100

    update translations (changed source code line numbers)

    Signed-off-by: Martin <Ho-Ro@users.noreply.github.com>

You could build your own version or request a package update based on the latest OH6022 release - there are a lot of improvements since November.

@jvandenbroek
Copy link

Sorry for my late response, but you are absolutely right. Didn't realize the git version of AUR was that outdated. Now I've installed the recently released regular version (also from AUR). The issue still persists with kvantum-dark, but setting Fusion style in settings solves this.

@Ho-Ro
Copy link
Member

Ho-Ro commented Aug 25, 2022

The issue still persists with kvantum-dark, but setting Fusion style in settings solves this.

Please unset Fusion, restart the program with OpenHantek --verbose 1 and report the startup messages, normally it should select "Fusion" automatically if it detects "kvantum*". But nevertheless it's good that you found a workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
User Interface Look and feel of the program
Projects
None yet
Development

No branches or pull requests

3 participants