QML and Qt Quick

@penpen said in Resizing of QQuickView very slow and flickering: I've found some solution that is not perfect but muche better than default behavior QSurfaceFormat format; format.setSwapInterval(0); format.setRenderableType(QSurfaceFormat::OpenGL); view.setFormat(format); Ho, i have the same problem and the same GPU: 1060 6gb. Some solution?

Another route is creating a custom image provider. With that you choose how to interpret the end of the url. The data will be provided to the Image item via a handler.

@HenkKalkwater thank you a lot. It works perfectly. [image: 8e7d0226-676f-445b-b628-1f1edab57c6b.jpg]

Oh, I know! thanks! When I used delete, some signals/slots were not nicely handled. Thank you, both of you.

One possible thing to do is rebuild the backend (and just the backend not the whole of Qt)

https://doc.qt.io/qt-5/qml-qtgraphicaleffects-dropshadow.html The path has to be drawn some how for this to work I think.

@HenkKalkwater said in QML: QMetaProperty::read unable to handle for some enums defined in C++, but not all: Anyways, a huge thank you for your help. I´ve been stuck on this for about 2 days. Your welcome, I am glad I could help you :)

@J-Hilk Thank you, the singleton approach works very well. I have created two functions *Messagging::instance()and *Messaging::qmlInstance(QQmlEngine *engine, QJSEngine *scriptEngine) and registered the second one as Singleton in my main file: Messaging *Messaging::instance() { if (m_pThis == nullptr) { m_pThis = new Messaging; } return m_pThis; } QObject *Messaging::qmlInstance(QQmlEngine *engine, QJSEngine *scriptEngine) { Q_UNUSED(engine); Q_UNUSED(scriptEngine); return Messaging::instance(); } Now, the same instance can be used in all other classes to edit variables and update GUI elements accordingly with e.g. Messagging *messageService = Messagging::instance(); messageService->setMessageText("xyz");

Hi and welcome to devnet, Go with Qt 6.1 as the graphical effects module is back in that version.

Replying to myself. The simple solution is not to use "function", but to just write the JS code in curly brackets. Didn't know that's even legal... text: { switch (lockKey.mode) { case first: return "First option"; case second: return "Second option"; case third: return "Third option"; default: return "Default option"; } } Sorry for the noise. I'll leave this for those searching for the error message (as I did).

All of my previous suggestion support the case when color rectangles are not equal. It's up to the implementation to handle it.

@manny_lp said in Release memory from QAbstractItemModel: qDeleteAll also does not help. ? What exactly is your issue? (Apart from the fact that you don't seem to actually call ListModel::clearItems())?

@Witzgy A workaround could be to pass the size through the url, something like image://colors/red?width=60&height=60, and in the provider obtain the size of the "id".