QML and Qt Quick

Hi, I solved by below edit but it is not good way. source: "file:///C:/Users/HP/Documents/Qt/Panel/car.png" Regards, Mucip:)

Thank you! I did not see your comment and tried with QQuickItem, it also worked! [image: 1a35fd2d-bfa9-4a61-b1d1-4931fcd7b1f4.png]

Yes, @GrecKo is right about the anchor, and the information about the SplitView.minimumWidth is misleading. Sorry about that.

It is probably best to avoid the Calendar from Controls 1 as it is deprecated in in Qt 5 and no longer exists in Qt 6. You could construct your own calendar with whatever behaviour you want using the components DayOfWeekRow and MonthGrid. These are in Qt.labs.calendar in Qt 5 but are in QtQuick.Controls in Qt 6 so there is a good upgrade path.

@GrecKo that's an interesting approach. Thank you for the idea! This thread could be considered as solved.

@DeSGuN Do you mean the border on only certain sides of the rectangle? I don't think there is a built in way to do this. You might be able to overlay thin rectangles to cover the borders perhaps, but I am not sure how well it will work.

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 } } }