Interesting. Well in that case I think I'll need to modify my code to
use ANGLE, as you are suggesting.
That'll require quite an effort so for the time being I'll stay with
QGLWidget.
Thanks a lot for your hints.
Calogero
Il 4/29/2015 11:31 AM, Agocs Laszlo ha scritto:
> Hi Calogero,
>
> When a
Hi Calogero,
When adding a QOpenGLWidget or QQuickWidget into a widget hierarchy in a
window, the entire window will be rendered differently: it is switched
over to OpenGL-based compositing. This involves using OpenGL features not
present in OpenGL 1.1.
If you avoid adding (parenting) the QOpenGL
Thanks Laszlo for your explanation.
I still do not understand why the whole application is not properly
rendered, not only the OpenGL stuff.
The application we are developing is a quite complex one, having
multiple windows, and the OpenGL one is a small part of it.
Simply including just one inst
Because when using remote desktop you are suddenly left with OpenGL 1.1
(ouch) and so QOpenGLWidget and friends that rely on OpenGL 2.0 features
(like framebuffer objects) cease to function.
The solution is to rely on ANGLE or a software rasterizer (like Mesa
llvmpipe) in this case.
When using th
Hi all,
switching my application from using QGLWidget to the new QOpenGLWidget I
noticed a very weird problem when using the application through Remote
Desktop on Windows. The whole application is fully black, it is not
properly rendered, not only the QOpenGLWidget, but also the other
widgets
