@ajcurtis said in QtCreator can not load plugins UBuntu 16.04:

QApplication: invalid style override passed, ignoring it.

But it is running now? If so then just ignore that warning.

Right, the library doesn't seem to be very Windows friendly. It assumes the pointers to GL functions resolved and available in global scope, which is not how it usually works on this platform. Moreover it seems to force ANGLE and OpenGL ES (or at least tries to) on Windows in the .pri file, but then is inconsistent in how it checks for that.

I'd say contact the authors and ask them to fix the Windows parts.

Sorry for the slow reply. Thanks both for your responses! I've had a quick look at GLSL #include before — I'm not exactly sure how to use it (this is a start though) — but apart from that, I'd prefer a way to do this in Qt, possibly more customizable and also driver-independent (e.g. I'm not sure if all graphics drivers support this GLSL extension). In addition to that, it would be a good feature to share with my students who might use Qt also for later/future projects.

I'm developing the software in an academic setting — when the (to be included) GLSL files have changed, things need to be (pre)processed again. Basically I wondered whether it's possible to automatically check .glsl files with a preprocessor for some tag (#pragma seems a good choice) and act on it, in this case use some sed/regex line to replace the mentioned file by the contents of that file. This could happen before every Build, or even before every Run (depending on how straightforward it is to save the copy-pasted version after Building and re-use it when Running, or just do this before every Run).

Did you try to put QCoreApplication::setAttribute(Qt::AA_UseOpenGLES); before initializing the webengine?

@chris2401
Hi I would guess on OpenGL 2.1 but could not find and doc either :)

Hi and welcome to devnet,

Did you try with QStackedLayout with StackingMode set to StackAll ?

Hope it helps

I found a solution and posted it on StackOverflow

Hi,

AFAIK, because that code is automatically generated. Although it would be nice to have a minimal information added for it's existence.

Might be an idea for a feature request on the bug report system.

Thank you @mrjj

hi
Did you chack?
what was the reason?
I'm going to make kind a same program, which one I should choose?

@Devopia53 I tested on Qt 5.8/Win7 today. The same incorrect result. But today i discovered the difference in overlaping behavior on my two machines. On the machine with video card fully-transparent widget has black color on white opengl context :D, where as other machine with integrated video card has no color(as should). So the gui transparency on opengl context is very platform dependent. Solution is to render widget by opengl directly but this way is very inconvenient. I think troll-tech must solve this problem in future.

Thanks !

@dalamber

Set QT_LOGGING_RULES environment variable to 'qt.qpa.gl=true'.

Here's my log, I'm not sure how to interpret it. It seems to say it's disabling ANGLE and using OpenGL, but I'm not sure and it conflicts with what CodeXL tells me.

qt.qpa.gl: Qt: Using WGL and OpenGL from "opengl32.dll" qt.qpa.gl: QOpenGLStaticContext::create OpenGL: "Intel","Intel(R) HD Graphics 5500" default ContextFormat: v4.4 profile: QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile) options: QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions),SampleBuffers, Extension-API present Extensions: 200 qt.qpa.gl: Basic wglCreateContext gives version 4.4 qt.qpa.gl: OpenGL 2.0 entry points available qt.qpa.gl: GPU features: QSet("disable_angle") qt.qpa.gl: Disabling ANGLE: GpuDescription(vendorId=0x8086, deviceId=0x1616, subSysId=0x80c2103c, revision=9, driver: "igdumdim32.dll", version=20.19.15.4549, "Intel(R) HD Graphics 5500") qt.qpa.gl: QWindowsOpenGLTester::supportedRenderers GpuDescription(vendorId=0x8086, deviceId=0x1616, subSysId=0x80c2103c, revision=9, driver: "igdumdim32.dll", version=20.19.15.4549, "Intel(R) HD Graphics 5500") renderer: QFlags(0x1|0x20) qt.qpa.gl: QWindowsIntegration::createPlatformOpenGLContext QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) qt.qpa.gl: "ARB::choosePixelFormat Attributes: 0x2003 , 0x2027 , 0x2010 , 0x1 , 0x2001 , 0x1 , 0x2014 , 0x18 , 0x2011 , 0x1 , 0x2022 , 0x18 , 0x2013 , 0x202b , 0x201b , 0x8 , 0x2023 , 0x8 , 0x2041 , 0x0 , \n obtained px # 5 of 1 \n PIXELFORMATDESCRIPTOR dwFlags=0x8225 PFD_DRAW_TO_WINDOW PFD_SUPPORT_OPENGL PFD_SUPPORT_COMPOSITION PFD_DOUBLEBUFFER iPixelType=0 cColorBits=32 cRedBits=8 cRedShift=16 cGreenBits=8 cGreenShift=8 cBlueBits=8 cBlueShift=0 cDepthBits=24 cStencilBits=8 iLayerType=0 cAlphaBits=8 cAlphaShift=24 cAccumBits=64 cAccumRedBits=16 cAccumGreenBits=16 cAccumBlueBits=16 cAccumAlphaBits=16 " qt.qpa.gl: ARB::createContext Creating context version 2 . 0 3 attributes qt.qpa.gl: QWindowsGLContext::QWindowsGLContext 0x163adc0 ARB requested: QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) obtained # 5 ARB QSurfaceFormat(version 4.4, options QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile)) PIXELFORMATDESCRIPTOR dwFlags=0x8225 PFD_DRAW_TO_WINDOW PFD_SUPPORT_OPENGL PFD_SUPPORT_COMPOSITION PFD_DOUBLEBUFFER iPixelType=0 cColorBits=32 cRedBits=8 cRedShift=16 cGreenBits=8 cGreenShift=8 cBlueBits=8 cBlueShift=0 cDepthBits=24 cStencilBits=8 iLayerType=0 cAlphaBits=8 cAlphaShift=24 cAccumBits=64 cAccumRedBits=16 cAccumGreenBits=16 cAccumBlueBits=16 cAccumAlphaBits=16 swap interval: 1 default: ContextFormat: v4.4 profile: QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile) options: QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions) HGLRC= 0x30000

One thing I note is that surprisingly my Intel GPU seems to be used rather than my AMD GPU.

Try changing Z:/disable_angle.txt to Z:\disable_angle.txt Note the backslash :) It's Windows, so this may be the culprit.

Apart from disable_angle (your config seems correct to me), try also setting disable_d3d11 and disable_d3d9.

I tried both of these things, but CodeXL still shows the same "D3D" symptoms.

Assuming you have an OpenGL context and you can draw/create objects in it you would make that context current, then create a QOpenGLPaintDevice and use it to render() the widget into that. Please note that a widgets require a QApplication instance and a running Qt's event loop, so you would need to ensure you have that.

As for DirectX Qt doesn't have any direct support for it, but you could probably grab() a widget into a QPixmap, transfer the pixels to a DirectX texture and draw a quad with it.
If you feel adventurous you could also implement your own QPaintEngine, then subclass QPaintDevice to return that engine and use it like with the OpenGL version.

Well, I have no other ideas, sorry.

i tried to use as many Gl functions instead of qt to use my old working code. But there is still nothing displayed. That's driven my crazy.

https://git.rwth-aachen.de/carstenf/OpenGL/tree/master/MeshViewerQt

Is there any way to see the content of the buffer while runtime???

@Stefan-Monov76
The automatic deletion of QObject childs by the parents is used in whole Qt frame work and
is fully documented and will not change in any version.
http://doc.qt.io/qt-5/objecttrees.html

Hi,

I'd recommend checking out the bug report system to see if it's something known. If not then please consider opening a new report providing your sample application as well as system specification.

Thanks Wieland for taking a look. And thanks for the mailing list suggestion! Good to know of more Qt resources.

I've filed a bug: https://bugreports.qt.io/browse/QTBUG-56774

@Stefan-Monov76 said in What are those string "name" properties set to various objects in Qt Canvas3D code?:

I just don't know what the purpose of setting it is.

Me neither, sorry. The only thing that I gather from the docs is that all Canvas3D objects have name parameter, much like QObject/ QML QtObject, so perhaps it can be used to search objects by name. It's only a guess, though.

@Stefan-Monov76 Good to hear that it works! :-) Regarding your question: I don't know, sry.