QGLWidget: Strange rendering offset on Windows
-
We are currently in the process of converting our application to Qt5. In some places the application still uses the outdated QGLWidget together with Coin/SoQt (Open Inventor) and also direct OpenGL rendering. Basically, everything works fine, except for an offset that all QGLWidgets show, i.e. rendering is shifted to the lower left and therefore cut off. I found a bug entry for this (https://bugreports.qt.io/browse/QTBUG-77340) but the problem also occurs with Qt5.14.
The strange thing is that this problem only occurs with two-monitor systems and when the application is started on the second monitor. For us this bug is a blocker at the moment, because the application is not usable and understanding that this issue is connected to the second monitor is not easy to see.
-
We are currently in the process of converting our application to Qt5. In some places the application still uses the outdated QGLWidget together with Coin/SoQt (Open Inventor) and also direct OpenGL rendering. Basically, everything works fine, except for an offset that all QGLWidgets show, i.e. rendering is shifted to the lower left and therefore cut off. I found a bug entry for this (https://bugreports.qt.io/browse/QTBUG-77340) but the problem also occurs with Qt5.14.
The strange thing is that this problem only occurs with two-monitor systems and when the application is started on the second monitor. For us this bug is a blocker at the moment, because the application is not usable and understanding that this issue is connected to the second monitor is not easy to see.
@Michael_Gaehwiler said in QGLWidget: Strange rendering offset on Windows:
I found a bug entry for this (https://bugreports.qt.io/browse/QTBUG-77340) but the problem also occurs with Qt5.14.
What happens if you use an older version, say Qt 5.6? Or even Qt 5.0?
-
I could narrow it down to a specific Qt version where this bug is introduced:
- Qt5.11.0 is fine
- Qt 5.11.1 is showing this issue
The bug report https://bugreports.qt.io/browse/QTBUG-77340 is now reflecting this.
