Never mind, I figured it out. I had to write a slot that gets connected
to QOpenGLContext::aboutToBeDestroyed(). This did the trick.
Kyle
On Tue, 2019-01-08 at 11:52 -0500, Kyle Edwards wrote:
> Hello all,
>
> My application has a QOpenGLWidget inside a QDockWidget. I initialize
> my shaders, te
Hello all,
My application has a QOpenGLWidget inside a QDockWidget. I initialize
my shaders, textures, etc. in the initializeGL() call as required.
However, when I undock the QDockWidget from the main window,
initializeGL() is called again. At this point, there's no way to safely
destroy the old r
gt;
>
>
>
>
> --
> *From:* Interest on
> behalf of Alexandre Ribeiro
> *Sent:* Monday, March 27, 2017 11:58:55 PM
> *To:* interest@qt-project.org
> *Subject:* [Interest] QOpenGLWidget inside QDockWidget
>
> Hi,
>
> I've p
regards,
Laszlo
From: Interest on behalf
of Alexandre Ribeiro
Sent: Monday, March 27, 2017 11:58:55 PM
To: interest@qt-project.org
Subject: [Interest] QOpenGLWidget inside QDockWidget
Hi,
I've placed a QOpenGLWidget inside a QDockWidget and everything works as
expected.
Ho
Hi,
I've placed a QOpenGLWidget inside a QDockWidget and everything works as
expected.
However when I drag the dockwidget from the main window there's a blue
flicker in the QOpenGLWidget. This blue flicker has nothing to do with my
OpenGL code (right now it's merely clearing the background with r
