QML and Qt Quick

@GrecKo below the code showing how the LogoMenuItem is used: Menu { id: logoMenu x: parent.width - logoMenu.width y: parent.height LogoMenuItem { text: qsTr("General Settings") defaultIconSource: "qrc:/Resources/images/Launcher/ContextMenu/settings_default.png" hoverIconSource: "qrc:/Resources/images/Launcher/ContextMenu/settings_hover.png" iconWidth: 21 iconHeight: 23 } LogoMenuItem { text: qsTr("Support") defaultIconSource: "qrc:/Resources/images/Launcher/ContextMenu/support_default.png" hoverIconSource: "qrc:/Resources/images/Launcher/ContextMenu/support_hover.png" iconWidth: 21 iconHeight: 16 } LogoMenuItem { text: qsTr("Log Out") defaultIconSource: "qrc:/Resources/images/Launcher/ContextMenu/logout_default.png" hoverIconSource: "qrc:/Resources/images/Launcher/ContextMenu/logout_hover.png" iconWidth: 21 iconHeight: 19 } LogoMenuItem { text: qsTr("Mobile App") defaultIconSource: "qrc:/Resources/images/Launcher/ContextMenu/mobile_default.png" hoverIconSource: "qrc:/Resources/images/Launcher/ContextMenu/mobile_hover.png" iconWidth: 17 iconHeight: 24 } LogoMenuItem { text: qsTr("Exit") defaultIconSource: "qrc:/Resources/images/Launcher/ContextMenu/exit_default.png" hoverIconSource: "qrc:/Resources/images/Launcher/ContextMenu/exit_hover.png" iconWidth: 21 iconHeight: 22 onTriggered: Qt.quit() } background: Rectangle { implicitWidth: 220 // Changing this value has no effect color: "#21212D" } } onClicked: logoMenu.open() The parent is Menu {}

Yes and no. No: I did not solve it the way I have imagined it. Yes: I changed DummyData to be QML_SINGLETON and use QQmlEngine::singletonInstance to get the pointer to the instance in the C++ code.

Hi ! Same issue for me after upgrading from 6.4.2 to 6.8.1. In my case, I'm setting orientation in "main.cpp".

I did some more research and it seems this is the way to do it: // This code must be placed directly in the ListView WheelHandler { acceptedDevices: PointerDevice.Mouse property int speed: 2 property Flickable flickable: parent.parent onWheel: (event) => { let scroll_flick = event.angleDelta.y * speed; if(flickable.verticalOvershoot != 0.0 || (scroll_flick>0 && (flickable.verticalVelocity<=0)) || (scroll_flick<0 && (flickable.verticalVelocity>=0))) { flickable.flick(0, (scroll_flick - flickable.verticalVelocity)); return; } else { flickable.cancelFlick(); return; } } } Hope this helps someone.

@Victor-Manuel said in Qt android reports generator: but their libraries are not compatible with armelf_linux_eabi You can build them by yourself for armelf_linux_eabi

Nevermind this behavior already seems to happen

@pillexyz_z. Good news. Move the ticket to solved as well.

@SGaist Using import QtQuick.Controls.Material auto in qmldir, I found that there is no need to use template for SplitView.

Hi @crimson1023 I have leaved a comment with the new updated project you can see that in the link. My problem now is that I can't rotate the dials correctly.. Also thank you @JoeCFD but I don't understand how to set the connection between my C++ class and my QML code. I must use the connections but I can't write the code properly

@dheerendra Amazing🥳！It works,but why could not it run correctly before?I think thery are similar,just a little different.Is the problem on the order of the property?🧐

Is is also odd that the binding loop detector does not complain about the line above where is it claiming a binding loop which ostensibly appears to be binding in a similar way: x: control.background.x + control.background.width / 2 - width / 2 Correction if I reorder these two lines I do get a binding loop warning for x: control.background.x + control.background.width / 2 - width / 2 but not for y: control.background.y + control.background.height / 2 - height / 2