Do these objects output by the factory have a lifetime that needs to exceed the QML component used for the object's controls? If not, I would make the object a QML (not Quick) type, and have the component that displays the controls also instantiate the object. Even if they do have lifetimes that don't match the UI portion, the controls can be thin wrappers around the objects that really implement the backend. In the example below RadioBackend and TapeBackend are QObject derived classes that export Q_INVOKABLE functions and properties for communication with the UI. Register them with one of the qmlRegister* functions, depending on the desired interface. For example: Radio.qml: Rectangle { color: control.colorTheme RadioBackend { id: control } Row { Button { onClicked: control.doAction() } Button { onClicked: control.doOtherAction() } } } TapeDeck.qml: Rectangle { color: control.colorTheme TapeBackend { id: control } Button { onClicked: control.doTapeAction() } } main.qml: Loader { property MediaType mediaType source: mediaType === MediaType.Radio ? "file://Radio.qml" : "file://TapeDeck.qml" }

If I create the dots dynamically, are there different ways of doing it? I have never done that before.

f3 = new QFrame(); ??? How can I have a fixed size for the buttons for both the situations? c->setSizePolicy(QSizePolicy::Fixed,QSizePolicy::Fixed);

@SGaist Thanx mate :) Qt rox :D

@jsulm thanx bro :)

@Lasith Well, emit a signal, pass the current value to it as parameter. Connect the signal to the slot. // somewhere in your code connect(this, SIGNAL(mySignal(int)), otherObject, SLOT(mySlot(int))); for (int i = 0; i < 10; ++i) { emit mySignal(i); } // In the other class void MyObject::mySlot(const int value) { // Do something } Did you read http://doc.qt.io/qt-5.9/signalsandslots.html ? Actually you should think about the need of signals and slots in this particular case - maybe it will be much easier and faster to directly call a method from the other class instead of emitting a signal? Signals/slots are useful if you want to have loose coupling, so the sender does not need to know anything about receiver.

Hi While walking my imaginary dog, i was wondering if the number you input "ui->values->text().toInt()" means how many names/ages to get and you mean for it to ask that many times, and not really create that many dialogs ? So like ask me 10 times and one and the same dialog would show up 10 times ? And each time, user press ok, it would save the data, then show again ?

@monster You can create the TextInput using createComponent and then after creating its object you can assign it to a js variable. You can store them for eg. in an array for further reference. var component = Qt.createComponent("MyTextInput.qml"); var textinput = component.createObject(parent);

@Dong Hello, Sorry for the late reply. Yes, you've got the essence of it. Qt's containers (QList included) are pretty smart in respect to copying, they will not copy the actual data until you change it. They are implicitly shared. This is done so you can return and copy the container many times, but in actuality internally only a pointer is reassigned and reference counter updated. When you call a non-const function on that list, Qt checks the reference counter and if more than one object is attached to the data, then and only then the data is detached (copied). When you put your list in the QVariant it is stored by value (making a shallow copy), but QVariant will return a shallow copy as well (meaning the data will not be changed, only the internal pointer reassigned and reference counter incremented). Now, for your particular case: The first line of code works, because you don't modify the list, but take an element (which is a pointer) and modify the object the list is holding reference to. This doesn't cause the list data to be copied. The second line you have, doesn't work, because you're changing the list data (assigning a new value to a list's element), which causes the list data to be detached and in practice, you're operating on a completely different set of data. Here is a reference if you're interested in the way QList and other containers manage their data, and what implicit sharing is.

Hi @Pisko and Welcome, The first problem is that I don't know how to definite the button id if i create them dynamically so I cannot identify which buttons are pressed to save the answers in the database. Unfortunately you cant assign an id for dynamically created items. Check this for more details. Another problem is that I cannot create Exclusive Groups dynamically. I think you can use a ExclusiveGroup here.

@Mephi Hmm, sorry for that. I wasn't aware of it as i have never used it before. So digging in it seems that the attached properties of DelegateModel doesn't seem to work if the delegate is in separate file. Could be a bug I suppose. You can try reporting it here.

@Basstrom Hi both ways would work with different information. It is possible to give each widget a name with number if needed. But if you are aiming for something that would be a table then it is far more work to create a widget for each column than to use a QTableWidget as sgaist suggests. ui->table->setRowCount ( 1 ); ui->table->setColumnCount ( 3 ); ui->table->setSizePolicy ( QSizePolicy::Expanding, QSizePolicy::Expanding ); ui->table->setHorizontalHeaderLabels ( QString ( "Name;Track Time;Prev Track Time" ).split ( ";" ) ); //Add Table items here ui->table->setItem ( 0, 0, new QTableWidgetItem ( "Michael Schumacher" ) ); ui->table->setItem ( 0, 1, new QTableWidgetItem ( "22.55" ) ); ui->table->setItem ( 0, 2, new QTableWidgetItem ( "44.3" ) );

Yes. mAppEngine is instance of QQmlApplicationEngine. I would like to assign one model to one ListView(in case of many tabs created). I tried this: SmsModel *model = new SmsModel(); model->createDummyData(); QObject* pRoot = mAppEngine->rootObjects()[0]; QObject* m_pTabView= pRoot->findChildren<QObject*>("conversationTabView").first(); if (m_pTabView) { QVariant returnedValue; QVariant title = phoneNumber; QQmlContext *context = new QQmlContext(mAppEngine, mAppEngine); context->setContextProperty(QString("myModel"), model); mAppEngine->rootContext()->setContextProperty("mmm", model); QQmlComponent *component = new QQmlComponent(mAppEngine, QUrl("qrc:/ChatView.qml"), this); QObject *object = component->create(context); QQmlEngine::setObjectOwnership(object, QQmlEngine::CppOwnership); object->setProperty("active", QVariant(true)); component->setParent(m_pTabView); QMetaObject::invokeMethod(m_pTabView, "addTab", Q_RETURN_ARG(QVariant, returnedValue), Q_ARG(QVariant, title), Q_ARG(QVariant, QVariant::fromValue(component))); object->setProperty("anchors.fill", "parent"); } and in QML: Rectangle { ... ListView { model: myModel } } I get this error "ReferenceError: myModel is not defined". When I do mAppEngine->rootContext()->setContextProperty("myModel", model); I have data in GUI, but when I create two tabs, then both ListViews share the same model(I want one model <-> one ListView).

Below is an answer. void MyWidget::changeEvent(QEvent *event) { if (e->type() == QEvent::LanguageChange) { titleLabel->setText(tr("Document Title")); ... okPushButton->setText(tr("&OK")); } else QWidget::changeEvent(event); } code within if (e->type() == QEvent::LanguageChange) { ... ) should contain ALL the code which has to be called when language changed. Basically every line of the code with tr() has to be called there. In there you can put call to retranslateUi, but retranslateUi is just a function where QtDesigner put strings created in there. this might be or might not be sufficient for your widget. Finally there are people who do not use designer. That is why you could not find retranslateUi mentioned anywhere. Keyword is tr(). For example you may fill tree widget outside of designer. If you used text which has to be internationalized there, you need to make sure the same code is executed as a reaction on language changed. Common logic suggests to put all code which requires initialization in a single function or slot. Such function or slot should be called when QEvent::LanguageChange arrives. Call this function myRetranslateUi if you want. You do not have to subclass every widget (as suggested by example) though. Alternative is to install event filter.

@nickaein My only advice is to make things as clear and understandable as possible. ColumnLayout and RowLayout are just convenience forms of GridLayout, and personally I think it's confusing to know exactly what each attached property Layout.somethingdoes :).

Still looking for a solution to this, any ideas?

Hi chocis, Yes Yes, otherwise container will contain a bunch of undefined objects. The objects are destroyed immediately when destroy() is called and their memory is also freed immediately (the javascript garbage collector is not involved in this case). The objects are instantiated immediately when createObject() is called, but they are rendered the first time after returning from the onClicked javascript code block. Don't know. You need to measure. If your targeted hardware supports multiple threads: Create the objects outside the GUI thread. Either use incubateObject() in QML or do it in C++ with QThread. In addition: Create invisible objects when the CPU / GUI thread is idle and set them visible as soon as you need them. Don't know. You need to measure. Send signals from QML to other (C++) threads to terminate them. Don't know. Like you already stated, if the component you want to instantiate isn't in a separate qml file then Loader can't be used. Try incubateObject(). Cheers! Wieland