up (8 chars)

It should be supported indeed. Did you try with a more recent release of Qt ? Like 5.15 or even 6.2 ?

Here are all the WGL functions https://docs.microsoft.com/en-us/windows/win32/opengl/wgl-functions The function of interest is wglMakeCurrent https://docs.microsoft.com/en-us/windows/win32/api/wingdi/nf-wingdi-wglmakecurrent The line of interest is "A thread must set a current rendering context before calling any OpenGL functions. Otherwise, all OpenGL calls are ignored." so, what I recommend is to call wglMakeCurrent(NULL, NULL); (or whatever the Qt equivalent is.) from your GUI thread. Then, in your other thread, make a context current by calling. wglMakeCurrent(hdc, glcontext); (or whatever the Qt equivalent is.) and now, you can make gl funciton calls. When you are finished, call wglMakeCurrent(NULL, NULL); then, release the GL context, destroy the GL context and all that stuff.

@wrosecrans Yes, I'm rendering using a QOffscreenSurface on a separate thread then displaying the frame on a QWindow on the GUI thread, but it makes sense to have all of the video rendering on the same thread so we're not interfering with the GUI thread. I've successfully tested this concept with GLFW-based OpenGL windows and QT UI. I doubt Vulkan will be any different since from what I understand the render window will still need to sit on the GUI thread.

The problem is solved please check this https://forum.qt.io/topic/113640/solved-why-q-window-events-are-eaten-by-qml-item thanks

Hi Hmm, nope. it looks very much like the sample with some code from TriangleWindow::initialize() in the render() function.

@marcbf said in Remember window size before maximization (or Detect if QResizeEvent is maximization): int w = currentSize.width(); int h = currentSize.height(); if (restoresize) { w = qMax(settings["Width"].Value(0), w); h = qMax(settings["Height"].Value(0), h); } Man, this is the deal!!! Everything worked perfectly after I fine tuned your code to my context! Thank you very much. The trick was really to use normalGeometry and windowState, so these two are the answer to my question.

@mrjj Thanks for the reply! I followed your advice and tried setting the panelWindow as the parent... No change.. Any other ideas? I followed this link, http://doc.qt.io/qt-5/qmacnativewidget.html#details

@mrjj yeah!! its working bro if i remove label.. Thank you all for your suggestions

@pmendl No problem. Do bear in mind that if you decide to send the event with QApplication::sendEvent, you are responsible for the event object's deletion, so it's a good idea to create it on the stack in that case. Good luck! Kind regards.

It's not very well exposed, but this is actually documented in QPainter::begin(): Warning: A paint device can only be painted by one painter at a time.

@Wieland Thanks for the help and the link. Do you know any desktop environment where showMaximized doesn't work? No I do not. I'm contributing to an open source project so I want to be sure.

@SGaist Ok I guess i'll open a different question for this issue, thanks anyway for your help

@p3c0 Hey thanks! Works as expected. Another baby step on the road to writing more interesting bugs. . . ;-)

Hi, You could try with an eventFilter and handle QEvent::InputMethod in there Hope it helps

Can you try to first go full screen and only then create the embedded QWindow ?

I found out the solution using native Windows Gestures WM_Gesture. By default QT registers QMainWindow-Window as a Touch Window, so the QMainWindow-App only get WM_Touch events. As said above one can only get either WM_Touch event or WM_Gesture event. So you have to unregister the window from getting Touch event. I do that in the constructor like this: HWND myHwnd = reinterpret_cast<HWND>(this->winId()); PULONG flag = 0; bool istouch = IsTouchWindow(myHwnd,flag); if(istouch) UnregisterTouchWindow(myHwnd); now i get WM_Gesture events in nativeEvent: bool OpenGLWindow::nativeEvent(const QByteArray & eventType, void* message, long* result) { MSG* msg = reinterpret_cast<MSG*>(message); switch(msg->message){ case WM_GESTURE: case WM_GESTURENOTIFY: emit sendNativeEvent(eventType, message, result); break; } return false; } Thanks for your help.

Hi, Sounds like you may have found a regression. You should take a look at the bug report system to see if it's something known. If not please consider opening a new report providing a minimal compilable example showing the behavior

There is a static function of QWidget that will create a container widget with a QWindow as a parent. QWidget* QWidget::createWindowContainer(QWindow *,...) Once you have the widget container this can be the parent of any other dialogs or widgets you need to add.