Qt Quick default window, using the mouse to stretch the window size with black borders
-
I created a new QtQuickApplication project using Qt Creator without any changes to the code. I used the mouse to drag and drop the edges of the window, and the speed was extremely fast. The window instantly displayed a black border.
@NeosYang I had the same problem and posted here. Nobody had a working answer. I stuck to qt widgets cause of this, most things are more stable over there.
Tested it on: Windows 10, 64bit with MinGW64 and LLVM, QT 6.7 using a NVDIA Graphicscard GTX 1050 Ti. AMD Ryzen 5 3600X.
-
DAMN this thing is a problem with the core functionality of QML ... why hasn't this been fixed??? Or are we the only 2 persons experiencing this?
-
Hi,
Since 6.8 came out, did you try it ?
-
@SGaist Just tried it with qt 6.8 the issue still persists. And as said it affects even the out of the box examples by QT themselfs...
-
Then the next step is to check the bug report system to see if there's something related.
-
This is a known issue, see https://bugreports.qt.io/browse/QTBUG-120051. As you can see in the comment section, this is quite a tricky problem and not only Qt is affected by it. As far as I know, we were able to fix it on Apple systems but didn't find a D3D API (yet), that would allow us to do the same for Windows.
-
This is a known issue, see https://bugreports.qt.io/browse/QTBUG-120051. As you can see in the comment section, this is quite a tricky problem and not only Qt is affected by it. As far as I know, we were able to fix it on Apple systems but didn't find a D3D API (yet), that would allow us to do the same for Windows.
@Matthias-Rauter Thanks alot, really a pitty tho i haven't experienced this problem with other graphicssoftware such as photoshop, aftereffects, blender, godot, affinity photo.
But well im neither experienced enough to make suggestions on how they might do it or how to make it better, just wondered and of course hoping for the best. ;)
-
I am currently writing in Chrome and it struggles with the same issue. I don't like it but I wasn't aware of it until right now. So hopefully your users won't notice either.
There are also some workarounds mentioned here, but they all have downsides: https://bugreports.qt.io/browse/QTBUG-107198 If this is really important to you, you might want to try those.Anyway, we will stay on it and try to fix it :)
-
I am currently writing in Chrome and it struggles with the same issue. I don't like it but I wasn't aware of it until right now. So hopefully your users won't notice either.
There are also some workarounds mentioned here, but they all have downsides: https://bugreports.qt.io/browse/QTBUG-107198 If this is really important to you, you might want to try those.Anyway, we will stay on it and try to fix it :)
@Matthias-Rauter Yep thank you
This fixes it completely, but sadly no GPU acceleration than
QQuickWindow::setGraphicsApi(QSGRendererInterface::Software);Also setting to this makes it better but not gone:
QQuickWindow::setGraphicsApi(QSGRendererInterface::OpenGL);Using Vulkan or init setting is the worst:
QQuickWindow::setGraphicsApi(QSGRendererInterface::Vulkan);Idea: Use qt widgets for the mainwindow and embed a qtquick view with vulkan rendering for the gpu acceleration? Good or bad?
-
Bumpin my question: Use qt widgets for the mainwindow and embed a qtquick view with vulkan rendering for the gpu acceleration? Good or bad practise?
