QML and Qt Quick

Hi and welcome to devnet, While I understand the lock you are into, testing with a more recent version can help you check whether what you actually have is working. Two possible outcomes: it does and you can try to back port the changes needed it does not and you have to check if it's an issue (and possibly fill a new ticket about it)

So what did you had to do with your code to make it work ?

I found the solution, shortly after having posted : I was missing acceptedButtons: Qt.AllButtons

Thank you Vitalii777 and SuhasKrishanamurthy for your help. Much appreciated! The code above working good.

@JKSH Thanks for the answers!

@Dika The solution is to: Register your class using QML_SINGLETON Do not call qmlRegisterSingletonType<>() If you don't have (or don't want) a default constructor, implement a static member function called create() to act as a factory. See https://doc.qt.io/qt-6/qqmlintegration-h-qtqml-proxy.html#QML_SINGLETON for an example

It looks like it won't be possible to rebuild the old project without migrating the code to Qt 6...(

@StudentScripter said in Feedback needed: QML is this the right way to link other QML Files?: removing RESOURCE_PREFIX / is no problem, works still fine, thanks. :D Good to hear, that's what I expected :) There were some changes in Qt 6.5 to make things easier, so you should no longer need to specify RESOURCE_PREFIX unless you want some unconventional structure (which is not recommended) However do you mean changing all mymodules mentions to mymodulesplugin or only this one? I meant only one: target_link_libraries(appQmlLibraryTest PRIVATE Qt6::Quick mymodulesplugin # <-- Like this ) Cause when changing only one it gives me errors. Can you please share the full error message? Without it, it makes it hard to troubleshoot for you. @StudentScripter said in Feedback needed: QML is this the right way to link other QML Files?: Also another question what to do if i wanted to add another subfolder inside my mymodules/ directory? Lets say: mymodules/extras You could create a new QML module (in mymodules/extras/CMakeLists.txt)

@MattP2 I don't see how this works. Depending on your input/original color you will get a different gray value in the computation: color.rgb += brightness * color.a; float gray = dot(color.rgb, vec3(0.299, 0.587, 0.114)); Then this gray value will affect to colorizationColor in: color.rgb = mix(color.rgb, gray * colorizationColor.rgb, colorizationAlpha); So even if colorizationAlpha is 1.0, the gray affects the output. It would work, if color was clamped to (1,1,1) after applyiing the brightness, but that doesn't seem to happen. I always get my colorizationColor scaled in the result, even with brightness: 1.

What exactly are you trying to achieve ?

I have the same problem in 2025. Did you find a solution?

The layout only finalizes after the window is part of the scene graph, so showing it immediately causes visible resizing. Instead, set the QQuickView visibility to hidden or move it off-screen first. After creating and adding the QML component, wait for implicitWidth and implicitHeight to be valid (you can use a short QTimer::singleShot ). Then resize the window and show it—this way, the user only sees the final, correct size.

@jhayar Thank you, that makes sense. But ItemSelectionModel.Select doesn't work either. So I'm not sure what you are supposed to use there. Update: I figured out what the problem was. The standard practice is to use a bitwise or with SelectionModel objects. Also I got the index line wrong from the start. The below works: tableView.selectionModel.select( tableView.model.index(row, 0), ItemSelectionModel.Toggle | ItemSelectionModel.Rows) And now I have found out that selections made this way don't survive the filter proxy so I need to do my own logic anyway. Thanks for the learning.