General and Desktop

What problem are you running into? There are several existing X11 window managers that use Qt, so nothing in Qt should prevent it from working. Ultimately, a WM is just another X11 client like any other application. There's nothing inherently "special" about it. A "connection between X and Qt" would basically just be creation a QApplication object. That will create a connection to the X Display. QWindow can go to/frame a native window Handle: https://doc.qt.io/qt-5/qwindow.html#fromWinId You'll need something like that if you want to do things like reparenting windows from other processes

@jsulm Sorry, it's my fault. I write wrong parameters at lamda function :(;;;

@jsulm Thank you for your reply. Let's try it.

I can relate to the points you raise regarding the use of transformations. Some years ago, I have written pretty much what you describe, but I was never happy with the complex code that resulted. It worked well, though, except for two issues which I couldn't find a solution for: Cosmetic pens of width != 1 paint super slow (I needed them to keep a constant line width while zooming). Here the solution would be, as you write, to calculate everything up front and paint in screen space, but the code was too progressed to make that change I used QGraphicsProxyWidget to integrate QScrollbars into my scene, which sometimes simply wouldn't repaint, no matter what I did (5.15.2, might have been fixed later) Now, I am involved in coding a similar component from scratch, using QML and SceneGraph. QML for layouting and custom QML components written in C++ for the heavy lifting. It seems to work rather well, but documentation and exacmples on SceneGraph are thin.

@DungeonLords hi from the looks of the source tree you can use either qmake or cmake. The CMakeLists.txt is geared for Qt 6.

ok, got it working! Added "-lOLEAUT32" to win32:LIBS and added the following to the separate QThreads run function (whenever i used them) and the main function: winrt::uninit_apartment(); winrt::init_apartment(); So to condense all of this into one post (for those who are also trying to do what im doing): .pro: CONFIG += c++20 QMAKE_CXXFLAGS += /await:strict win32:LIBS += -lwindowsapp -lOLEAUT32 main.cpp: #include <winrt/base.h> int main(int argc, char *argv[]) { QApplication a(argc, argv); winrt::uninit_apartment(); winrt::init_apartment(); return a.exec(); } QThread derived classes: #include <winrt/base.h> class DerivedThread : public QThread { public: DerivedThread (QThread* parent = nullptr) : QThread(parent) {} public: void run(){ winrt::uninit_apartment(); winrt::init_apartment(); exec(); } }; Those alone should get everything up and running to be able to use functions (aside from specific things like things requiring other things [looking at you collections...]) Now to create some qobject classes and get test out actual inputs! Thank you all for your help! Oh! Almost forgot this tidbit, make sure your build tools/sdk's are up to date! EDIT: Looks like derived threads dont need to have the unint/init_appartment functions.

@ananthavidhya There are examples in documentation: https://doc.qt.io/qt-5/qprocess.html Especially this one is what you need: QProcess gzip; gzip.start("gzip", QStringList() << "-c"); if (!gzip.waitForStarted()) return false; if (!gzip.waitForFinished()) return false; QByteArray result = gzip.readAll();

@RobertB said in Where is Qt5QuickConfig.cmake ?: -nomake tools This looks suspicious. Some of the tools you will need when building Qt Quick. Can you try configuring without? Also, are you sure the compilation actually succeeded? You can try by checking the return value: make -j10 || echo "FAILURE"

@jsulm Searching online I found this https://github.com/lucasg/Dependencies tool which supposed to be an updated version of the decencies walker. I managed to use cmd to output some of the dependencies my app needs. In CMD it prefixes the needed DLLS by category, for example it writes [WellKnownDlls] KERNEL32.dll : C:\WINDOWS\SysWOW64\kernel32.dll. So as far as I'm concerned none of the 'well known' DLL's should be copied. EDIT: I ended up making a python script that parses the output of this app and copies over files marked as [Not Found].

Can you please share your entire class definition / header file with us? Sorry for asking about this- we don't know what your thisactually is. Do you subclass QObject? Or QThread? Have you overridden virtual methods, e.g. QThread's run()? Have you added the debug statements I proposed and if so, what's their output?

@jsulm I'll give it a try.

@J-Hilk C:\Qt\5.15.2\msvc2019_64 That is all.

@mrjj thank you

@satyanarayana143 Did you try what I suggested?

@Desfell said in MVC pattern with QGraphicsItem: QGraphicsItem cannot emit signals :{ No but QGraphicsObject Class adds just that if it's what you are missing.

@Christian-Ehrlicher So, I have fixed it by adding this line: baseDir.mkpath(QFileInfo(absPath).absoluteDir().path()); Code: bool QZipReader::extractAll(const QString &destinationDir) const { QDir baseDir(destinationDir); if (!baseDir.exists()) { baseDir.mkpath(destinationDir); } const QVector<FileInfo> allFiles = fileInfoList(); for (FileInfo fi : allFiles) { const QString absPath = QDir::toNativeSeparators(QString("%1/%2").arg(destinationDir, fi.filePath)); baseDir.mkpath(QFileInfo(absPath).absoluteDir().path()); if (fi.isFile) { QFile f(absPath); if (!f.isOpen()) { f.open(QIODevice::WriteOnly); } f.write(fileData(fi.filePath)); f.setPermissions(fi.permissions); f.close(); } } return true; } Now, it creates all directories and extracts files. The issue is resolved. Thank you.