Re: [Interest] QML Window doesn't refresh its contents using Qt 5.7 and AA_UseOpenGLES

Hi all, I've filled a bug regarding this issue, just in case any of you is affected, and want to contribute: https://bugreports.qt.io/browse/QTBUG-54451 Cheers, Robert. On 28 June 2016 at 19:02, Roberto Garrido wrote: > Hi all, > we are using OpenGL ES as renderer in the windows

[Interest] QML Window doesn't refresh its contents using Qt 5.7 and AA_UseOpenGLES

Hi all, we are using OpenGL ES as renderer in the windows version of our app. Setting "QCoreApplication::setAttribute(Qt::AA_UseOpenGLES)" on app launch worked well until Qt 5.6, but with Qt 5.7 the contents of the window aren't refreshed in real time. I've recorded a couple of videos of the "Squi

Re: [Interest] Custom QSGGeometryNode Scene blending issue

or not. > > Or simply use QQuickFramebufferObject, of course :) > > cheers, > Gunnar > > > On 23 Jun 2016, at 17:26, Roberto Garrido < > robertogarridomar...@gmail.com> wrote: > > > > Gunnar, > > thanks for your detailed response. > > We don'

Re: [Interest] Custom QSGGeometryNode Scene blending issue

oject/playground-scenegraph/tree/master/shapes) > > Btw, if you used QQuickFramebufferObject instead of rolling your own > custom Item/node/material, you would get option 1 by default :) > > cheers, > Gunnar > > > On 06 Jun 2016, at 18:05, Roberto Garrido < > robert

[Interest] Qt 5.7 glGetError returns GL_INVALID_OPERATION in QSGGeometryNode::preprocess

Hi! We have just updated our Qt app (using a custom QQuickItem to render our OpenGL scene via QSGGeometryNode::preprocess) to use Qt 5.7. Calling glGetError the first thing in QSGGeometryNode::preprocess returns a GL_INVALID_OPERATION GL error. Any idea on why could be happening? Thanks in advanc

[Interest] Custom QSGGeometryNode Scene blending issue

Hi all! We have a custom QQuickItem which in turn creates a custom QSGGeometryNode. We reimplement the QSGGeometryNode's preprocess() method in order to draw our scene to a FrameBufferObject with a texture attached. This OpenGL texture ID is shared with the QSGGeometryNode's material. This way, we

Re: [Interest] Force Qt 5.4 to use ANGLE OpenGL ES 2 implementation

Hi Sean, and Andrew. The problem was that I was explicitly linking against OpenGL32. Now without that explicit link, the OpenGL ES 2.0 commands are working, and returning valid values. Thank you very much! Robert. ___ Interest mailing list Interest@qt-pr

Re: [Interest] Force Qt 5.4 to use ANGLE OpenGL ES 2 implementation

Hi, On 15 February 2015 at 10:08, Andrew Knight wrote: > >> > FTA, use the QT_OPENGL environment variable (set QT_OPENGL=angle) or the > application attribute (QCoreApplication::setAttribute(Qt::AA_UseOpenGLES)). > From your results below, it doesn't appear you've tried either. > > > Setting QCo

[Interest] Force Qt 5.4 to use ANGLE OpenGL ES 2 implementation

Hi all, We have a windows Qt desktop app that links to a rendering library based on OpenGL ES 2.0. We want to assure that the app will run on as much as devices as possible, so we think that using ANGLE is a good idea. My question is: is there anything we can do to force our Qt 5.4 app to use ANG

[Interest] Building Qt for android on Mac OSX using the crystax NDK

Hi all, We are porting our Qt Windows/MacOSX/iOS app to android. We have a huge codebase using boost serialization. Boost serialization relies on wide chars, which are not supported by then official NDK. So our plan is to build Qt against the crystax NDK. Anyone succeeded on building Qt 5 against

Re: [Interest] QQuickRenderControl example not working on Desktop OSX (Qt 5.4 Alpha)

On 16 October 2014 11:16, Gunnar Sletta wrote: > > On 16 Oct 2014, at 09:45, Roberto Garrido Martín < > robertogarridomar...@gmail.com> wrote: > > > Hi all, > > We have our OpenGL ES 2.0 based renderer. Until now, we were integrating > it into our Qt app by us

[Interest] QQuickRenderControl example not working on Desktop OSX (Qt 5.4 Alpha)

Hi all, We have our OpenGL ES 2.0 based renderer. Until now, we were integrating it into our Qt app by using a QML Item/Node configuration, but the new rendercontrol API in Qt 5.4 Alpha seems to be a more flexible solution, and the proper way to integrate. I’m running the rendercontrol example dis