QML and Qt Quick

A different image, but same effect. Fixed it with the BusyIndicator class. Button { text: "Run Blocking Function in C++" onPressed: busyIndicator.running = true onClicked: MyObjectInCpp.start() } BusyIndicator { id: busyIndicator running: false Connection { target: MyObjectInCpp function onFinished() { busyIndicator.running = false } } }

@firen I am not aware of such a page but you are not alone having that issue.

@Veltroniv the preferred Connections syntax is now: Connections { function onLoginCorrect(token) { console.log("Token: ", token); } }

@mzimmers said in How to order object creation: I can just use outcome directly (which is preferable). Please don't do that! That is called "unqualified access", which prevents the QML compiler from optimizing your code. See https://www.qt.io/blog/compiling-qml-to-c-fixing-unqualfied-access for a discussion about unqualified access See https://www.qt.io/blog/the-numbers-performance-benefits-of-the-new-qt-quick-compiler for a peek at the optimization Use property bindings correctly (without doing special construction and assignment in Component.onCompleted) and you should get things the right order: // main.qml Window { id: window property Outcome outcome: outcomeComponent.createObject(window) as Outcome Component { id: outcomeComponent Outcome {} } ListView { delegate: VspEdit { outcome: window.outcome } } } // VspEdit.qml ColumnLayout { id: vspEdit required property Outcome outcome Component.onCompleted: console.log(vspEdit.outcome) } Notice that I fully qualify my variables (window.outcome, vspEdit.outcome) property var outcome Use the actual type instead of var for more optimization (and also so that modern tools like qmllint can scan your code and help you find any issues)

@Ntachy I did this by creating my own clear function (I name it reset() ), where I set all the properties to their default values. In my case I had a button where the user would click to reset the values, dont know your use case, where you would called it is up to you. If you want to clear the values "outside" the running app, check here for where the values are stored: https://doc.qt.io/qt-6/qsettings.html#platform-specific-notes

@dheerendra Yes, the ListView in the both the pages will use the same model.

@Arev it's the pkgconfig configuration file. Each library / framework can provide it (or you can create your own).

@alpartis Try setting the overlay z: Overlay.overlay.z: 10000

QString webRTCUrl = QString::fromUtf8(UrlMessage); // Create and show WebRTC video viewer widget QWebEngineView view; view.setUrl(QUrl(webRTCUrl)); // Use the URL variable I have written this part of code to stream the video from camera bit it gives me black screen. Help me

@kim333 May be it is issue from your system ? Or Since you are calling qml methods directly from C++, something may be hung or got into deadlock ? There is no specific order of call. It is just method call. If it is multithread application & it may be work slightly differently. Best approach is write a small QML application. Use timer to continuously update the qml with some random text. Observe for the period you said. This may give you the hint on where the issue exist.

@zzzzxx - last time I had this problem, I'm pretty sure I solved it by installing OpenSSL. Also, make sure your device/laptop/phone has internet connection. I have a 10 year old Lenovo 64bit laptop. To be sure, I downloaded and installed both 32bit and 64bit OpenSSL; https://slproweb.com/products/Win32OpenSSL.html For me, to get the new image looking right; I made a few minor adjustments; Image { id: name fillMode: Image.PreserveAspectFit anchors.fill: parent source: "https://d2f9uwgpmber13.cloudfront.net/public/image_new/26fe75871805b8fa8ffcd1a94778be4c?.jpeg" }

@SimonSchroeder I think @J-Hilk's interest in using vi/vim in any shape or form is absolute 0! We were jesting back & forth.

@BlinCt Any solution?

@Markkyboy - solved it, answer staring me in the face. Have been using CircularSlider all wrong!, doh!

Hi, Based on the class documentation, the class is legacy and will only work if OpenGL is used in the backend. Try running your application with the QSG_RHI_BACKEND environment variable set to opengl. For example: QSG_RHI_BACKEND=opengl appopenGL.