Qt 5.9.8 shared build with MSVC 2019 issue

[Cobra91151]

Hi! I have compiled the Qt 5.9.8 shared with Visual Studio 2019. Now it compiles properly, but the issues with the code still exists:

And the button hover doesn't work. At first it was with the static build, but the same issue is present with shared also: https://bugreports.qt.io/browse/QTBUG-75280
It seems that the problem is only with graphics when Qt 5.9.8 built with VS 2019, but I can't confirm it. Has anyone check it or any ideas how to fix it? Is it the problem with Qt or VS 2019? Thanks.

[SGaist]

Hi,

You should provide a complete minimal compilable example project when you open a report. This will allow developer to replicate your issue more quickly and as close as possible as you are experiment it.

[Cobra91151]

@SGaist

Ok. I'm working on it. I will upload it soon.

[Cobra91151]

So, I have created the test example: TestHoverExample.zip. All source code and binaries are available in the .zip file.

Image of the issue TestHoverExample Qt 5.9.8 (MSVC2017/MSVC2019):

Also I added this information to bug report here - https://bugreports.qt.io/browse/QTBUG-75280#!kcRxkYDL!WZcWCzrGER9oCkxwoy8YL-_-hbndraz_4xUXgaojpTY

Thanks.

[JKSH]

@Cobra91151 Does the issue exist when you build Qt 5.12.3 with MSVC 2019?

Note: Qt 5.9.x will not be patched to add support for MSVC 2019.

[Cobra91151]

@JKSH

Hi! I can't check that because Qt 5.12.x does not support Win Vista. I only use Qt 5.9.x branch. But Qt 5.9.x branch got patched to build Qt WebEngine with VS2019. So, I think it might get this fix too. Also I think the problem is with ANGLE API (libEGL.dll, libGLESV2.dll).

[Cobra91151]

Also, after some checking, this issue only occurs in the Release mode.

[SGaist]

Please upload that zip on your bug report. A link to some net storage may die at any point.

[Cobra91151]

@SGaist

I tried but it limits me to 10 MB. I uploaded it to Mega it should stay as long as needed.

[JKSH]

@Cobra91151 said in Qt 5.9.8 shared build with MSVC 2019 issue:

I can't check that because Qt 5.12.x does not support Win Vista.

Hmm? Your screenshot and bug report both use Windows 10. Can you use your Windows 10 machine to test?

But Qt 5.9.x branch got patched to build Qt WebEngine with VS2019.

Oh, I wasn't aware of this. Where did you see this patch?

But anyway, note that Qt WebEngine is security-critical. See this post: "Qt 5.9 LTS is currently in ‘Strict’ phase and receives only the selected important bug and security fixes, while Qt 5.12 LTS is currently receiving all the bug fixes."

An issue caused by a new compiler is not likely to be fixed in Qt 5.9, s because you can still use an old compiler. However, if you can show that the issue still exists in Qt 5.12.3 with MSVC 2019, then it is much more likely to be investigated and fixed.

I tried but it limits me to 10 MB.

You only need to upload the source code. You don't need to upload the binaries.

[Cobra91151]

@JKSH

Yes, I use Win 10 for development, but for production it should be supported on Win Vista and later. Currently, I'm switching back to VS 2017. Source code has been attached to the bug report.

[JKSH]

@Cobra91151 said in Qt 5.9.8 shared build with MSVC 2019 issue:

Yes, I use Win 10 for development, but for production it should be supported on Win Vista and later.

I was only asking you to check if the issue exists on Qt 5.12 or not. I didn't mean you should upgrade your production version.

Currently, I'm switching back to VS 2017.

Since you need to support an old OS on an old version of Qt, it makes sense to stay on an old, tested compiler too.

Source code has been attached to the bug report.

Great, thanks.

[Cobra91151]

@JKSH

I'm going to check Qt 5.12.3 for such issue with MSVC2019. I will reply about it later.

[Cobra91151]

@JKSH

So, the same issue is present on Qt 5.12.3 built with MSVC2019 compiler:

I think the problem is with ANGLE API textures/shaders.

[pfandl]

I have probably the same issue here with 5.12.4. The progressbar has artifacts and also widgets in views tend to get them. I compiled with -opengl desktop and the issue goes away when replacing Qt5Gui.dll and Qt5Widgets.dll with those of the binary release from Qt.