@SeeRich
can you change

setAttribute(Qt::WA_StyledBackground); setObjectName( "mainWindow" ); setStyleSheet( QString( "MainWindow#%1 { background-color: blue; }" ) .arg( objectName() );

to

setAttribute(Qt::WA_StyledBackground); setObjectName( "mainWindow" ); setStyleSheet( QString( "QWidget#%1 { background-color: blue; }" ) .arg( objectName() );

there is no MainWindow stylesheet. It should be QMainWindow.

Here is the same question with a working example
https://codereview.stackexchange.com/questions/274781/qt-creating-a-dark-overlay-to-apply-on-top-of-other-widgets-with-animation

Thanks to all for the replies.

I finally resolved the issue by replacing the TableView by a ListView and rewriting the columns handling manually. As the ListView draws the whole item content once, all the above mentioned issues are resolved at the same time.

However very interesting concepts were presented here, and they may help me for other similar situations in the future. Once again, thank you very much to took the time to help me and reply to my questions.

@red.green
hi, I'm unfamiliar with the virtual keyboard.

But I have the following idea.

inside your TextField, you listend to onActiveFocusChanged if that becomes true, that the virtual keyboard should be called forth.

On you can than listen to the editingFinished signal and force the focus on the parent. to guarantee that the active focus is really gone after editing

Item{//arbitary parent TextField{ onActiveFocusChanged: if(activeFocus) //do stuff onEditingFinished: parent.forceActiveFocus() } }

Thanks for your reply.

This seems to have improved the situation somewhat, as I can now see the red image when I click. However, the original image seems to be overlayed over the top of the red image with a level of transparency. It's almost like the visible: false parameter is changed when the MouseArea is clicked?

It's somewhat hard to explain, hopefully the above makes sense?

If not, I can put together some screenshots to demonstrate the issue?

EDIT: Never mind, it looks like user error after all! I had the z-order configured incorrectly, so the drop shadow was being drawn on top of the image rather than underneath it. Thanks again for your help!

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.