On 2021-06-30 16:43, Michael Jackson wrote:
Replying to my own question (actually, not sure my first message made
it to the list), a helpful colleague found the following:


which leads to https://bugreports.qt.io/browse/QTBUG-68740 and
https://bugreports.qt.io/browse/QTBUG-68521. I have a small test
project that shows that those bugs are back with Qt 5.15.2 and 5.13.

Should I reopen the bug(s), start a new bug? I figure there is no hope
of getting them fixed with the current emphasis on Qt 6 but at least
if someone else experiences this issue then it might be nice to have
the issue documented.

Can you reproduce with the oldtestcase attached to QTBUG-68740 ?
If yes then it's the same bug and it should be reopened.

If only your new testcase can repro then it's a new bug. You reference the old bug in case there's any good insights.

I would also test with Qt6, as any fix should go there first.

I was able to reproduce the issue on macOS 10.14 and 10.15 but not
macOS 11 (Big Sur) and Windows 10. All were running the same conda
virtual environment. Same in the sense that the same commands were use
to generate each environment on each respective system.

Sérgio Martins | sergio.mart...@kdab.com | Senior Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel: Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - The Qt, C++ and OpenGL Experts
Interest mailing list

Reply via email to