QML and Qt Quick

I'm not sure if there is something like remote debugging for QML. Some thoughts: If you want to get current states of a QML application and check layouts at runtime etc. have a look at GammaRay. This tool allows you to examine and manipulate the internals of Qt applications at runtime, augmenting conventional debuggers by understanding the implementation of Qt. If you want to run tests and access your QML application you could check out SPIX, a testing framework. Spix is a minimally invasive UI testing library that enables your Qt/QML app's UI to be controlled either via c++ code, or through an http RPC interface.

@RokeJulianLockhart said in Does QML support native look-and-feel on Windows?: @JKSH, as aforestated, my environment isn't primarily Windows, so a pre-defined WinUI2/3-equivalent QQuickStyle is assistive, but not sufficiently comprehensive if I want to utilise QML. Ah, I missed that. This thread is about native look-and-feel on Windows so I answered in that context. OK, Qt Quick Controls also has native styles for macOS, iOS, and Android. (There's no such thing as a "native" style for Linux) My suggestion? Give Qt Quick a test run with a simple test project. Decide whether to use it or not based on how it helps you get things done, not just what styles are available. Other note: The graphics technology is called Qt Quick. The primary language is QML, but you can still use C++ to implement some Qt Quick classes if you wish. is all the information I see online about QtWidgets being deprecated in QML's favour (which KDE's push for Kirigami appears to mimic) because that was once true, but isn't anymore? Well, Qt Widgets was never deprecated in the first place. My guess is that people saw that each new release brought big improvements to Qt Quick but didn't bring big improvements to Qt Widgets, and concluded that widgets are being dumped. What they forgot was this: Widgets were a mature, 20-year-old technology that works well and is relied on by many, so there's no room for fancy revolutionary changes. Qt Quick was a new young technology, wet around the ears, with lots of room for growth. That's why the growth spurts seem so dramatic. However, I'm glad to hear that QtWidgets are in active development. I'm not sure I'd use the term "active development" though. It's being maintained, bugs are fixed, and it's kept working smoothly with new versions of OS'es, but there's no revolution happening.

You should ask the Qt support for help. They already did such kind of things and are for sure the better place to ask such questions.

I was afraid I would have to resort to hacks like this... Okay, I will try. Thank you.

TreeViewDelegate use model.display This help me contentItem: Item{}

simplified code: Image { id: exampleImage source: "example.jpg" anchors.fill: parent smooth: true } Text { text: "This is an example description." color: "white" anchors.fill: parent font.pixelSize: 16 wrapMode: Text.Wrap horizontalAlignment: Text.AlignHCenter | Text.AlignVCenter HoverHandler { id: textHoverHandler } opacity: textHoverHandler.hovered ? 1 : 0 Behavior on opacity { NumberAnimation { duration: 300 easing.type: Easing.InOutQuad } } }

@jsulm said in qtvideosink not work on embedded target: QT_DEBUG_PLUGINS hello jsulm, actually every looks good from the log perspective, the only problem is when I run app, there's only a empty windows without videotestsrc rendering. check the below log with QT_DEBUG_PLUGINS set to 1. also in the qml I have print mediaplayer status. from below it change from 2 to 6, still quite good. btw, I'm not able to attach log directly via code style, it is detected as spam, I don't know why. so I paste it here qtvideosink-debug-plugin

Could you put your complete code in one qml file so we can more easily test your exact setup?

PinchHandler and WheelHandler are for zoom. If you need to move the map you need DragHandler and TapHandler One of them rotates the map, I guess it's not what you want on mobile devices

Sorry, it work, problen in my model

Hello! Just for future visitors since this is the first page that came up in a google search. https://bugreports.qt.io/browse/QTBUG-122024

Ah, didn't know that. I never tried to build Qt from source.

Possible find real row like that: realRow: treeView.index(row, column).row

@Actarus said in QML file not found in resource system (qrc) despite correct qml.qrc configuration: I solved it using qt_add_resources() instead I'm glad to hear that you were able to resolve your issue. As the next step, I recommend taking the time to port from qt_add_resources() to qt_add_qml_module(): https://doc.qt.io/qt-6/qt6-port-to-qt-add-qml-module.html This provides your projects with benefits such as optimization by the Qt Quick Compiler (https://www.qt.io/blog/the-numbers-performance-benefits-of-the-new-qt-quick-compiler) and improved code analysis by your IDE.

@GrecKo that was the other idea. But It means creating a QML module just for dummy model used for ui prototype; and I don't like to release that module on production code. Example Form.ui.qml import com.myrealmodule import com.mydummymodule ... // Here I use singleton for dummy data ... However if I don't release that dummy module, clearly I have runtime problem when application starts, cause it.s not able to find It.

What I see with MultiEffect: [image: 625e447c-36c1-4ba7-b7ae-7a85e3bc9f45.png]