QML and Qt Quick

we have to define only one import statement for dialog component at a time. For my work, Qt.labs.platform 1.1 works fine so I discarded the other one. Like this,I have commented out the Dialogs component import QtQuick 2.15 import Qt.labs.platform 1.1 import QtQuick.Controls 2.15 import QtGraphicalEffects 1.15 import QtQuick.Layouts 1.15 //import QtQuick.Dialogs 1.3

@WilliamH07 I just tried to open the app, and it's nearly instantaneous, and it immediately locates itself upon opening. However, 5 seconds later, after closing and reopening the app, it takes 7 to 8 minutes.

@Anumas Thanks, I find out the really problem I got before, URI will composed with QT_QML_OUTPUT_DIRECTORY and the OUPUT_DIRECTORY parameter of qt_add_qml_module() to making some directories or target filename while building, and that cause conflicts

@afalsa said in Generalizing Animation Setup in QML: PropertyChanges { passwordRequeriment1.opacity: 0 passwordRequeriment2.opacity: 0 passwordRequeriment3.opacity: 0 } Thanks ! Work excellent!

I had a similar situation, I needed to create a new component 'button_Color' and move it to a new file 'button_Color.qml', I selected a block of code to transfer, pressed the right mouse button, but the item option 'refactoring' of the menuwas unavailable(gray), It was solved by accident, I move the mouse cursor to the beginning of code block 'button_Color' , Item {}, on the word 'Item', and press right button on mouse and get the menu with available item option of menu 'refactoring'

@MintogoDeveloper Hi, i am also following the blog post and trying to do the example he provided. But it seems i can't render anything out. Do you have some snippets of your code that can render something? Such that i can use it as reference

@jsulm It was solved. Thank you very much.

@Jenny-R I solved the problem by using this solution: https://stackoverflow.com/questions/58874314/animating-bearing-property-change-with-qml-map. Some additions and clarifications: I placed the RotationAnimation component on the same level as the MapView and placed the property "myBearing" and "onMyBearingChanged" inside the MapView component. The animation is then called from whereever the change should be triggered. I.e., a separate property (myBearing) is animated and every time the property is changed, setBearing() is called. alignCoordinateToPoint is handled in a similar way. Code example: MapView { id: mapView property real myBearing property geoCoordinate myCenter anchors.fill: parent z: 0 map { plugin: mapPlugin zoomLevel: 14 center: QtPositioning.coordinate(51.507622, -0.127855) } onMyBearingChanged: { mapView.map.setBearing(myBearing, predefinedAlignmentPoint) } onMyCenterChanged: { mapView.map.alignCoordinateToPoint(myCenter, predefinedAlignmentPoint) } } RotationAnimation { id: bearingAnimation target: mapView property: "myBearing" direction: RotationAnimation.Shortest duration: 1000 function startBearingAnimation(to) { bearingAnimation.stop() bearingAnimation.from = mapView.map.bearing bearingAnimation.to = to if (bearingAnimation.from !== bearingAnimation.to) { bearingAnimation.start() } } } CoordinateAnimation{ id: centerAnimation target: mapView property: "myCenter" to: QtPositioning.coordinate(newLatitude, newLongitude) duration: 1000 }

If anyone interested in the future, bug reported: https://bugreports.qt.io/browse/QTBUG-123573

@Ivelin It is really difficult to understand what you are trying to achieve. Are you trying to trigger the re-authentication like this? If so, what about this approach? Foo.qml import QtQuick import QtQuick.Controls.Material ApplicationWindow { id: root width: 640 height: 640 visible: true Material.theme: Material.Dark Loader { id: loader } function authenticate() { loader.sourceComponent = null loader.sourceComponent = barComponent } Component.onCompleted: root.authenticate() Item { anchors.centerIn: parent Label { id: label text: "Let's try this" anchors.centerIn: parent } } Component { id: barComponent Bar { onSucceeded: message => { label.text = "Succeeded " + message } onFailed: message => { label.text = "I'll try again because " + message root.authenticate() } } } } Bar.qml import QtQuick.Controls.Material import QtQuick.Layouts ApplicationWindow { id: root width: 320 height: 320 visible: true Material.theme: Material.Light signal succeeded(message: string) signal failed(message: string) RowLayout { Button { text: 'success' onClicked: { root.succeeded('yay!!') root.close() } } Button { text: 'failure' onClicked: { root.failed('I failed') root.close() } } } }

@ShaunaB1 I also thinking about using that way. (problem this way not simple for internalization)

Thanks for all the suggestions, everyone. I decided that emitting the signal directly was the most straightforward way to go. I didn't realize that any of those possibilities even existed...I guess I haven't found the documentation that explains this.