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

Broken GUI layout #10

Closed
jflesch opened this issue Nov 10, 2015 · 6 comments
Closed

Broken GUI layout #10

jflesch opened this issue Nov 10, 2015 · 6 comments
Labels
GUI An issue with the graphical interface (not a bug, more of a glitch)

Comments

@jflesch
Copy link

jflesch commented Nov 10, 2015

Hello,

I just tried installing Openhantek on GNU/Linux Debian. It seems there is a major problem with the layouts of the elements of the GUI. It makes a lot of features unusable.

Here is how it looks like

GUI elements can be rearranged by the user, but when restarting OpenHantek, everything is a mess again.

Distribution : GNU/Linux Debian Jessie (8.2), 64bits
WM: Gnome 3 (dual screen)

Thanks in advance,

@geissdoerfer
Copy link

Same configuration and same issue for me. Apparently there's some buggy threading. If i try to change some settings (AC/DC):
QObject: Cannot create children for a parent that is in a different thread. (Parent is Hantek::Control(0x1c37960), parent's thread is QThread(0x1a2fdb0), current thread is Hantek::Control(0x1c37960)

@davidgraeff
Copy link
Member

The current GUI is written in pure c++ and therefore not very maintenance friendly. I'm working on a successor written in a declarative style and with the current technology (Qt QML) in the other branch but still on holiday at the moment :)

@OliverHaag OliverHaag added the GUI An issue with the graphical interface (not a bug, more of a glitch) label Nov 26, 2015
@OliverHaag
Copy link
Contributor

The threading issue and the GUI issue seem to be unrelated on first sight to me. I agree with David though - best wait for the QML rewrite and recheck both issues then.
Back in the Qt 4 times pure C++ was the best way to do it imo but nowadays I would also use QML since it's just much easier maintainable. Most probably some things have changed with Qt 5 (Guess Qt 5 was used, but this wasn't specified in the reports).

@geissdoerfer
Copy link

Ah okay i thought it was related, as for me the functionality is also affected and it kind of looked like the GUI elements could not communicate with control parts. Haven't had a closer look though tbh. Also i'm not sure about which Qt i was actually using, will check and try both. Anyway @davidgraeff, had a look into your branch and it looks very promising 👍 The killer feature for me would be a clean programmatic interface, that i can wrap for matlab/python

@cskau
Copy link

cskau commented Dec 10, 2015

I ran into the same issue a couple days ago, and I went in an created a fix for at least part of the issue in this PR:
#11

I do not think this is related to threading.

@davidgraeff
Copy link
Member

In my setup this problem is fixed, please open another issue if it is not for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GUI An issue with the graphical interface (not a bug, more of a glitch)
Projects
None yet
Development

No branches or pull requests

5 participants