General and Desktop

This "bug fix" reads a lot to me as though it's the source of my problem... Ugh. https://codereview.qt-project.org/c/qt/qtbase/+/314377

@Christian-Ehrlicher Thank you very much for the help and sorry for the identical post.

@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.

@paulmasri which version of Qt 5 are you using ?

@quutee sounds like it's a bug. You should check the bug report system to see if there's something related.

@SGaist, Qt 6.3.2, Windows 10. I found that winapi coordinates I got eventually turned out to be different from QCursor::pos() when talking about switching between different scales. So I decided to use QCursor::pos() instead, and it helped: QPoint globalCursorPos = QCursor::pos(); auto menuGeom = ui.qMenuBarMain->geometry().translated(ui.qMenuBarMain->mapToGlobal(QPoint(0, 0))); if (menuGeom.contains(globalCursorPos)) //some work

@Anna-Honorey Hi and welcome, this is indeed very basic C++. You should learn that first (or while learning Qt) otherwise you will have a hard time learning and understanding Qt C++. Header and source files are there because of multiple things. It helps to organize your code and separates your implementation of classes and function from their declaration. As you might have seen, this is just a "standard". You might come across short programs, which only have a main.cpp, where everything is declared and used. The main.cpp is the main entry point for your C++ program. How are they connected? You #include <test.h> your header in your test.cpp to use the function declared there. This article may help https://cplusplus.com/articles/Gw6AC542/

@MScottM Mixing QML and C++ is ok and you have to do that. But it is different from mixing two main windows of QML and QWidget. QWidgets != C++. I would recommend you to use QWidgets or QML only, better not both.

@JonB Thanks for your reply, I solved the problem according to your description

@azhagan2 https://doc.qt.io/qt-6/qabstractslider.html#value-prop https://doc.qt.io/qt-6/qabstractslider.html#maximum-prop

@robsparrow has the buffer size to be 1024? Have you tried any other numbers for comparison?

@Pythonic-person Unreal Engine allows you to build it as a library and embed into another app, provided that you can drive it. It needs native window messages and I'm not versed enough in python to give you specifics, but it sounds doable. Make sure to read through the UE EULA though, to be sure that whatever you plan to do is legally allowed by Epic. Just as a comment though. You chose a very slow language (python) to do very expensive task (3D), bind it to a C++ library (pyqt), which adds overhead, interoperate it with external app that has no direct python API, and then drive it with native OS messages in a language that is not directly supported by that platform. In short you chose to do it the hardest and slowest possible way before you even started. It's your decision of course, but I would seriously reconsider.