QML and Qt Quick

Would i be viable to use qt widgets and just use qtquick for all the other widgets embedded into the qt widgets mainwindow or is this a bad idea?

As I said in my original post, I have crossed FHD recording, the issue is with 4K... I want to understand whether QT/QML has the capability to support this...

Great ! Then please mark the thread as solved so other forum users may know a solution has been found :-)

This is how it is done, with the help of ChatGPT!; Canvas { id: canvas width: 400 height: 400 rotation: 180 anchors.centerIn: parent onPaint: { var ctx = getContext("2d"); ctx.clearRect(0, 0, width, height); / / Get the name of today var today = new Date(); var dayName = Qt.formatDate(today, "dddd").toUpperCase(); //var dayName = "wednesday".toUpperCase(); // Arc parameters var centerX = width / 2; var centerY = height / 2; var radius = 430; var totalArcLength = Math.PI * 0.24; // The length of the arc (3/4th of a circle) // Calculate dynamic letter spacing based on available arc length and number of letters var letterSpacing = totalArcLength / (dayName.length - 1); var startAngle = (Math.PI - totalArcLength) / 2; // Center the text on the arc ctx.font = "44px Mono Bold"; ctx.textAlign = "center"; ctx.textBaseline = "middle"; for (var i = 0; i < dayName.length; i++) { var angle = startAngle + i * letterSpacing; var x = centerX + radius * Math.cos(angle); var y = centerY + radius * Math.sin(angle); ctx.save(); ctx.translate(x, y); ctx.rotate(angle + Math.PI / 2); // Rotate the context to align the text along the arc ctx.fillText(dayName[i], 0, 0); ctx.restore(); } } Component.onCompleted: canvas.requestPaint() } }

@ceydasimsekk said in Unknown component: I think I made the necessary definitions. Where did you make the necessary definitions? Is this an edit-time error, build-time error, or runtime error? (It could be one or more of these) Also, what version of Qt are you using? And what's your build system -- CMake, qmake, or Qbs?

You have to use the Q_DECLARE_INTERFACE and Q_INTERFACES macros

@ceydasimsekk said in Qt does not see the icon: @JKSH I understand, thank you very much. I'm new to Qt. You're most welcome. And great choice! 😄

awsome bro ！！！！ it`s usefull for srcoll horizental listview by mouse wheel ListView { id: root clip: true model: [1,1,1,1,1,1,1,1,1,1,1] orientation: ListView.Horizontal spacing: 10 ScrollBar.horizontal: ScrollBar {} MouseArea { property int speed: 5 anchors.fill: parent onWheel: (event) => { let scroll_flick = event.angleDelta.y * speed; if(root.horizontalOvershoot !== 0.0 || (scroll_flick>0 && (root.horizontalVelocity <=0)) || (scroll_flick<0 && (root.horizontalVelocity >=0))) { root.flick((scroll_flick - root.horizontalVelocity), 0); return; } else { root.cancelFlick(); return; } } } }

Welp, even though I think the docs says that the directory containing the current file is automatically part of the import path, it doesn't seem to be the case. If I do this, it works: QML_IMPORT_PATH=. qml -style MyStyle test.qml

Can you provide a minimal compilable example that shows this issue. That way it will be easier to help you find the issue.

@GrecKo Hi no, I think it`s important property that must be add to VideoOutput module. any way : simple solution is what @diego-qt said but there is another solutions like ShaderEffect and QAbstractVideoSurface.

Why is that ?

I also faced this problem, try using "layer.enabled: true" for your main QML element. It was also effective to use “QCoreApplication::setAttribute(Qt::AA_UseOpenGLES);” in C++, but for me personally this was not acceptable, because the project used other rendering methods.

@Christian-Ehrlicher I'm sorry I didn't make it clear. I mean integrated into projects that use VS2002. If not, what about VS2012 or other higher version?

Hi @Imynn , I just faced the same problem and was able to solve it the following way. The problem is that from the documentation there is always 1 element in a SplitView that fills the width (height for vertical). And by default it is the last one. By regulating that element depending on the window width you can choose which one changes width along with the window. So I set red.fillWidth to false and blue.fillWidth to true when the window width is less than the threshold. I even did smth like splitview.onResizingChanged: if (!resizing) userBlueWidth = blue.width; // saving the blue width on the splitter drag release fillerRectIndex: Window.width < userBlueWidth + splitter.width + red.minWidth ? blueIndex : redIndex Red { SplitView.fillWidth: fillRectIndex == redIndex } Blue { SplitView.fillWidth: fillRectIndex == blueIndex } Then the blue becomes the filler and starts shrinking. Good luck!