QML and Qt Quick

@r3d9u11 and when you bind the row layout's width to the parent width? RowLayout { width: parent.width ... } So, all Controls on the right side will disappear (because their positions are out of application's width). I don't know why, looks like another bug. Not a bug, the minimumWidth will rise, but never shrink.

@sierdzio Thanks!

Apparently just a placeholderText: configwatch.patientID Works fine ! Sorry about that, I thought that I had already tried this...

For VideOutput that does the trick: VideoOutput { ... layer.enabled: true smooth: false } Unfortunately, it does't work with ShaderEffetct (the image is still blurry): ShaderEffect { ... layer.enabled: true smooth: false scale = 10 }

property variant items:[] items[i] = comp.createObject(root, {x: i, y: i*50}); Now you can access the any objects in items using index.

@sierdzio I think the url you provided is using a model. Is it possible to expose the QVariantList in the form of ( QList<QPair<int, double>>) to QML without using models. Can someone please provide a sample examples

OK. Here is where I am with this: I have a QAbstractListModel that holds a QList of pointers to QML objects that I load with QQmlComponent component(&engine, QUrl("qrc:/TestGaugeStyle.qml")); if(component.status() != QQmlComponent::Ready) { qDebug() << "Not Ready: " << component.errorString(); } GaugePresenter *object = (GaugePresenter*) component.create(); QQmlEngine::setObjectOwnership(object, QQmlEngine::CppOwnership); Then I add the created component to the model: //GaugePresenterManager is a singleton that is designed to manage the //lifecycle of these gauge styles. It also holds the model reference. GaugePresenterManager::instance()->getModel()->addGaugePresenter(object); When I debug I can see that the model is holding the pointers to the GaugePresenter and everything seems right. This is where I am kind of lost. I tried creating a property Q_PROPERTY(GaugePresenterItemModel* gaugePresenterViewModel READ getModel) and then in QML I assign that property to the model of the SwipeView Repeater. SwipeView { id: swipeView anchors.fill: parent Repeater{ model: GaugePresenterManager.gaugePresenterViewModel } } but nothing is displayed. I imagine it is because the property is a pointer to the model and maybe QML doesn't know how to deal with that? Or maybe this just isn't the right way to do this. The TestGaugeStyle is just a QML document that holds a rectangle with some text that says "test". I am expecting that when I add the TestGaugeStyle to the Model, the SwipeView will display it.

@Markkyboy Thank you for your code but there should be only two lights, one black and the other green/red. We just need to add a yellow color for one second to the light when the state changes from "go" to "stop". That is, when the state is going to change from "go" to "stop" it firstly stops for one second with the yellow color and then becomes back for the rest of time space and with color black, like normal traffic lights but this specific version has only two lights!

Sorry for the confusion. I had downgraded from 5.15.2 to 5.12.10 the night I posted the test code, because I was having a problem using root setContextProperty in 5.15.2 in another app of mine. You are correct! I just retried it, and it works. There was a mistake in my local copy of the test code. I was using preventStealing: false (!),then had commented that out. That's not the proper value, and I'm not sure why I used the value false. Thanks for helping me overcome my mistake.

Would you mind sharing the code ? Additional formats can be supported in QtQuick, it requires a shader that converts the data.

@QTLeearn said in Creating multiple QML objects simultaneously: Qt.createQmlObject Not that I've used it, but from documentation that method will return one object. Returns a new object created from the given qml string which will have the specified parent, or null if there was an error in creating the object. So your example QML string seems not suitable. However, I expect (just my assumption) that multiple nested objects could be created from a QML string, given that just one of them is the parent of the remaining ones.

Put Splash inside MainWindow.qml and have that file control when the Splash is shown. Add property to MainWindow.qml. You could do this in one file: Component { id: customMainWindow MainWindow { loader: true // add this property to MainWindow Splash { } // add custom splash logic as needed } } Loader { sourceComponent: customMainWindow }