Unsolved Design problem between choice of single or multiple C++ models
-
@elfring . No, each gauge would only have specific name, its unit and value. And the value would be updating each second.
-
@milan said in Design problem between choice of single or multiple C++ models:
But what about the gauge parameters like Name, value, unit that is coming from the model
@VRonin said in Design problem between choice of single or multiple C++ models:
setData to store in different roles all the data you need for the gauge (e.g. min, max, current value, tick distance, colour, etc.)
@VRonin said in Design problem between choice of single or multiple C++ models:
The method you want to reimplement is QStyledItemDelegate::paint. From there you can use index.data(role) to retrieve the data stored in the various roles of the model before
@milan said in Design problem between choice of single or multiple C++ models:
I also forget to add that gauge is Circular gauge from QtQuick2 extras used as quickwidget in QtWidget application
Ok, so performance is already out of the window, so you can use this template delegate to make the delegate part a lot easier. You just need to reimplement
setSubEditorData
to pass the relevant parameters to the widget -
@milan said in Design problem between choice of single or multiple C++ models:
No, each gauge …
It seems then that you are using a widget with well-known properties.
Will you eventually pass the name to a label? -
@elfring. Yes, each gauge has to be identified. So the label text will be updated by the model.
-
@VRonin . Could you please explain why the performance will be problem. What could cause that.
-
@milan said in Design problem between choice of single or multiple C++ models:
Could you please explain why the performance will be problem. What could cause that.
It's due to the way widgets are painter. Whatever the reason though you should ignore the performance issue, as it's (highly) unlikely you'd have tens of gauges, much less thousands of them.
-
@milan said in Design problem between choice of single or multiple C++ models:
Could you please explain why the performance will be problem
I'm not saying it will be a problem but it's certainly not optimised. You are mixing 2 UI frameworks one painted inside the other so it's only natural it won't be as performing as manual painting on a
QStyledItemDelegate
subclass -
@kshegunov . There will be around 10-20 gauges i think in a tab, another tab will use same model's data and name to display in Qt Charts.
-
@VRonin. I did not like to use two UI frameworks, but I did not find nice gauge in Qt Widgets. But using QML for a desktop application, I find it not easy.
-
@milan said in Design problem between choice of single or multiple C++ models:
but I did not find nice gauge in Qt Widgets
At the end of the day it's an arch, 2 triangles, some tick lines and some text. It's not hard to paint manually and a "gauge" allows so much personalisation that it's hard to ship a generic pre-made widget that satisfies everyone