QML and Qt Quick

@Cyrille-de-Brebisson Q_PROPERTY(QList<MyObj*> liste READ getliste NOTIFY listeChanged) now emit the listeChanged signal everytime you change the list If you would implement a QAbstractListModel subclass you would have more control of rearrangements etc.

@Tee_ normally a pro file results in a separate target (executable or library). Even if you "combine" them with a subdirs project. So your AppUi project must link against the AppLib

You could draw a line on top. Not ideal. Edit: Width of 1 rect with border.

@caicx said in Conditional Import: import QtGraphicalEffects 1.0 // Required by Qt 5.x.x vs import Qt5Compat.GraphicalEffects // Required by Qt 6.x.x yes and? Since the major version of Qt has changed you should also advance with your project, instead of importing a compat module of a previous version for the whole lifespan of Qt 6. The compat module is intended to be used as a quick solution until the porting of your application to Qt6 has finished

@jsulm - Thank You

@J-Hilk No, I haven't considered it because it has been working fine until now. Sorry, I made a mistake, it's "5.15.2" to be exact. I created a new project with the exact same settings and the exact same code, and it worked. Was there a problem with the settings that I missed somewhere?

Didnt know about breaking bindings yet and I feel like I dont understand the code onActivated well. What does => means / how it's named? Currently the custom item is defined like this: LeftBind { id: enabler x: 291 y: 15 keyName: keyTranslator.getKey(Config.enabler) //Config.enabler is vkey (int), this function converts it to readable string (for example from c++ vkey 0x10 to "ALT") onAccepted: { var a = keyTranslator.getCode(keyName); // from string to vkey if(a === 404){ askForKey() } else { Config.set_enablerBtn(a) } } }

@JoeCFD I was working on other stuffs but now I remember why I can't override QQuickItem update() method... it is a non-virtual slot, so it can't solve my rendering issues. I am still looking for a solution ...

@jeanmilost Your logic seems to be correct. What you have to do is to move the re-calculation of Scrollbar size & position to the Rectangle rcPageContainer because you are applying scale for that. Rectangle { id: rcPageContainer objectName: "rcPageContainer" ... /// called when page viewport width changed onWidthChanged: { sbHorz.size = rcPageViewport.width / rcPageContainer.width sbHorz.position = Math.min(Math.max(sbHorz.position, 0.0), 1.0 - (sbHorz.size)); } /// called when page viewport height changed onHeightChanged: { sbVert.size = rcPageViewport.height / rcPageContainer.height sbVert.position = Math.min(Math.max(sbVert.position, 0.0), 1.0 - (sbVert.size)); } }

Okay. Thanks. I would have tried to use the QML2 path!

It's work. Thanks Result [image: Screenshot_20211128_143000.jpg]

Thanks for the tip on Stackoverflow, I can see that QT6Guid is Allocating that memory but never releases it. Also there is Unresolved Allocation which I don't know what it is. The test was : Set the window to minimum size Take Memory Snapshot Resize the window by dragging the mouse multiple time Take a Memory Snapshot Repeat One more time Anybody have a clue on what's happening? Unresolved Allocation Qt6Guid.dll!QGles2GraphicsPipeline [image: 858fb3b1-d888-439c-923a-c05dec1c9fcb.png]

The following link provides the information about Qt /QML application coverage analysis and looking for any similar Plugins from forum. Hoping to hear soon. https://forum.qt.io/topic/61133/tug-framework-open-source-gui-unit-testing-for-qt-applications