A simple question: How to update multi form on mainwindows. use view and model ?

[Xrtero]

for example , on following image:

i want to update name , when server modify the user name.

[Pl45m4]

@Xrtero

Yes, either a model which fetches the data and updates the view or you send update manually via signal&slot to your display field.
Depends on how much data you have, how you want to organize it and what you want to do with it.
Implementing your own model + view just to update the first name / last name, is not worth it if you ask me.
If you have more data and want to store multiple datasets, it's probably the cleanest and best way.

[JonB]

@Xrtero
Consider using QDataWidgetMapper. That provides a two-way mapping between widgets and model, so changes in the model update the widget and if the user changes the widget that updates the model.

But depends what you mean by "when server modify the user name". If "server" means database server (like MySQL) you will not get a "notification" if a different process updates a database table, that is not supported.

[Xrtero]

@Pl45m4
thanks , i think both are ok.
but , a model was cleanest way. i will choose according to the actual situation.

[Xrtero]

@JonB
"server" means http server (like when i want get the username ,age ... etc )
so ,as the number of labels increases, the use of signals and slots becomes progressively more complex.
Moreover, if a single page needs to include various types of information ( i meaning different model objects),it will becomes particularly complicated . Using a model and view approach will make the core more simple(just use setModel to update view) . that's my impression as beginner.

[Pl45m4]

@Xrtero said in A simple question: How to update multi form on mainwindows. use view and model ?:

"server" means http server (like when i want get the username ,age ... etc )

So you make HTTP requests? With QNAM?

as the number of labels increases, the use of signals and slots becomes progressively more complex.

Using more signals doesn't make you app more complex, esp when they just update a string/int in a LineEdit.

Moreover, if a single page needs to include various types of information ( i meaning different model objects),it will becomes particularly complicated

The approach @JonB suggested is still viable. You can map these kind of information to the correct field where they are displayed.

Using a model and view approach will make the core more simple(just use setModel to update view) .

setModel does not update anything. It only assigns the model to the view.
For a custom model/view there is still a lot to do (re-implement functions, handle your use-case)...

that's my impression as beginner.

...might not be that easy, as a beginner :)

[Xrtero]

@Xrtero thank your reply, i think i know what i should do.