QML and Qt Quick

Yes that's exactly what I meant, thanks for explaining it Bob64.

@SetupIa Take a look at this example: https://doc.qt.io/qt-6/qtmultimedia-video-qmlvideo-example.html

i tried "link with qt", but result is the same.

If your shadow is cut off, I recommend to choose a bigger padding rect. What was a surprise for me - the x and y should be positive numbers if you want the rectangle to "wrap" top left corner too. Try something like: paddingRect: Qt.rect(100, 100, 300, 300) The size should be as small as possible though, cause it affects performance.

One of the (probably new) dependencies of the labs platform plugin is missing. You have to use the dependency walker directly on the plugin, to see which one it is.

@JKSH Agreed!

@GrecKo As expected, I get (-1, -1) cell coordinates back for non-visible indices.

@JKSH Thx. Will try it today.

@Tom-asso hi, Check the build log, you likely have a warning about that issue from the compiler.

I would be interested in this too. I happened across ColourImage in some Qt source the other day and thought it looked useful before realising that it's internal. This was in 6.8. I am porting some Qt5 code at the moment and was trying to figure out how to colour an svg. I used to use GraphicalEffects and the compatibility library isn't available with the in-house Qt build I have to use. Meanwhile MultiEffect, which I understood to be the Qt 6 replacement, doesn't appear to work, with no clues provided as to why not.

@GrecKo Thanks for the tip. In the Qt 5 tree view, the index was provided directly to the delegate but I see that it has to be derived from the row and column that are provided to the delegate in Qt 6. So I need to make sure I use the provided index() method on the tree to do this, rather than going directly to the model.

My professional guess is that Connections is specifically designed to reference a QtObject or null, ensuring type safety and clarity in signal connections. Source is a more generic term in QML, commonly used for properties like Image.source or Component.source, which refer to the data or component being displayed or instantiated.

Confusing indeed: https://bugreports.qt.io/browse/QTBUG-130864

This did it - thank you so much, I've been trying to figure this out forever.

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