Qt 5.12 Release Combo Box -> Bug! Bug! Bug!
-
You are telling it is not just a Designer issue. When you run the program also you see the same behaviour. Can you download from official release and then see it ?
Also wait for final release of 5.12.x. If you see the same, then file a bug.
-
@X-Crack said in Qt 5.12 Release Combo Box -> Bug! Bug! Bug!:
I don't know how to feedback BUG, if anyone will submit a BUG, please submit.
Well, see this https://wiki.qt.io/Reporting_Bugs
-
@X-Crack I don't know. I don't know what your app is doing. Do you use style-sheets?
Did you delete the build directory and rebuild completely then with Qt 5.12?
Just a note: there is no need to write "Bug!" 3 times in the title. -
@aha_1980
Sorry, my project is complicated to build.
I am a statically compiled QT source code.
But the problem is already very clear.
I believe that more people will react to the same problem in the near future.This kind of problem can also be presented in the official installation package given by "Qt Creator".
You can try it!
-
@X-Crack said in Qt 5.12 Release Combo Box -> Bug! Bug! Bug!:
I am a statically compiled QT source code.
This is something you should have said at the beginning!
You're not using official build.
My guess is that you're missing the correct style in plugins/styles.I just tried on my Windows 10 machine with Qt 5.12 MinGW - it looks like it did before. So, I cannot reproduce your issue.
-
Please start the program, reproduce the bug, and while the combo is doing whatever it isn't supposed to do click "pause" in the debugger. Then extract the stack trace(s) and upload them for us to inspect. It's impossible to tell what's going on without any information about what's being executed (i.e. no source, no stack).
Every time I click on the drop-down box "Combo Box", I start a thread.
Why do you do that?
PS
Ah okay, I understand now what the problem is. I have no idea why you get that. My advice is to try it as follows:
- The precompiled packages that come from Qt Company
- In a clean virtual machine. Also one that's not localized.
- Finally if 1 and 2 fail, try with a localized virtual machine
If it's present in case 1, 2 or 3, then I'd suggest filing a bug report on the tracker.