General and Desktop

I was able to get it to work under windows now I need to get it to work in linux.

I just saw that QVncServer is part of the commercial offering. I would recommend checking with the Qt Company as that module's code does not seem to be available.

@Christian-Ehrlicher Tank you very much for your reply. This was indeed the problem

Hi @Chasing_Light, your thoughts are correct, this code tries to access private API. You should use the exactly same Qt version as the training course, then it should work. Regards

I figured out the issue. Buffer upload must be done before beginPass() is called.... in render function, this line resourceUpdates->updateDynamicBuffer(m_vbuf.get(), 0, sizeof(vertexData), vertexData); needs to be before this line cb->beginPass(renderTarget(), clearColor, { 1.0f, 0 }, resourceUpdates);

That's really helpful. thank you.

After countless hours of debugging solution was really REALLY obscure. I had my QURL for QQmlApplicationEngine set to a loading screen then creating the App component from there. Qt really did not like this. returning the Original App.qml as my main URL and then running engine.load for my loading screen. engine.load(url); engine.load("qrc:/qt/qml/ExplorariumContent/LoadingScreen.qml"); TLDR: I used a very buggy method to load the app which caused ListView to freak out. Component { id: appComponent App {} } Connections { target: loadingScreenManager function onLoadApp() { var appWindow = appComponent.createObject(null) appWindow.effect.start() Qt.callLater(function() { root.close() }) } }

Alright I finally solved the issue. I added this to my CMakeLists.txt set(sources main.cpp) qt_add_resources(sources res.qrc) And ${sources} in the qt_add_executable list So now this is on top of my CMakeLists.txt set(sources main.cpp) qt_add_resources(sources res.qrc) qt_add_executable(4-WindowDifference WIN32 MACOSX_BUNDLE main.cpp mainwindow.cpp mainwindow.h res.qrc ${sources} )

Ok, thanks all. Looks like the application I downloaded was broken. The distributor didn't include everything that would allow it to run on a basic system. Thanks to everybody for your answers.

@SGaist I know it's a macro, I've already tried expanding it myself; the result was exactly the same. I'll try to analyze the generated code, thanks.

@blossomsg There's no reason for that slot to be in the model. Depending on how you want to integrate that with Maya, create your own custom view on top of the model that will translate that information in whatever is needed for Maya. A "view" does not mandatory mean a tree or a table, it's really whatever uses the model as a source of information.

I can't test this ancient version but would guess you installed a static Qt version. Therefore all is linked directly into your executable which explains the size.

I faced the same behavior, which was unexpected and undocumented. I was debugging Qt, and at the end there is the following fallback in their code. int registerHelper() const { if (d_ptr) { if (int id = d_ptr->typeId.loadRelaxed()) return id; return registerHelper(d_ptr); } return 0; } int QMetaType::registerHelper(const QtPrivate::QMetaTypeInterface *iface) { Q_ASSERT(iface); auto reg = customTypeRegistry(); if (reg) { return reg->registerCustomType(iface); } return 0; } qtbase\src\corelib\kernel\qmetatype.cpp

At a glance, it's not obvious that the xcb QPA (qtbase/src/plugins/platforms/xcb/xcb.pro) plugin won't work with recent macOS if the requisite supporting libraries and headers are present. Homebrew lists a few potential matches for "brew search xcb", including "libxcb".