Qt5 QSplitter : slow performance with OpenGL



  • HI all,

    I just tested adding OpenGL to a splitter using three different objects (one at a time);
    QGLWidget, QGLVIew and QOpenGL, and all of them resulted in slow performance and Qt sent a message "QBackingStore::flush() called with non-exposed window, behavior is undefined" to the console, even with a straight forward QGLWidget object. This is in Qt5.

    The same QGLWidget code was also tested in Qt4 and I didn't experience any lagging at all in interaction.

    What could be the problem? Or should we attach an OpenGL canvas differently?

    Thanks.

    Best Regards,
    Faizol



  • hi all,

    I just posted a question in the game development section regarding Qt5 splitter and OpenGL;

    I couldn't delete the previous post so I 'll just link it here as this is about Qt5 and I believe it'll get more response here.

    (http://qt-project.org/forums/viewthread/21339/)

    I just tested adding OpenGL to a splitter using three different objects (one at a time); QGLWidget, QGLVIew and QOpenGL, and all of them resulted in slow performance and Qt sent a message “QBackingStore::flush() called with non-exposed window, behavior is undefined” to the console, even with a straight forward QGLWidget object. This is in Qt5.

    The same QGLWidget code was also tested in Qt4 and I didn’t experience any lagging at all in interaction. What could be the problem? Or should we attach an OpenGL canvas differently?

    To the MOD, sorry for the double postings and I couldn't find the way to delete the previous post. Can the previous post be deleted?

    Many Thanks.

    [[Merged these two threads as the poster obviously intended to move the first one, Tobias]]



  • Hi all,

    the regression is done and verified;

    https://bugreports.qt-project.org/browse/QTBUG-27734
    Change By : Samuel Rødal (14/Nov/12 3:21 PM)
    Status : Verified
    Fix Version/s: 5.0.0 RC 1


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.